tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pid <...@pidster.com>
Subject Re: Connection has been abanded
Date Thu, 01 Dec 2011 10:17:33 GMT
On 30/11/2011 21:15, János Löbb wrote:
> Hi,
> 
> IT  is  Mac OSX 10.6.8  
> java -version
> java version "1.6.0_20"
> Java(TM) SE Runtime Environment (build 1.6.0_20-b02-279-10M3065)
> Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01-279, mixed mode)
> tomcat is 7.0.21
> database is Sybase ASE 15.0.3
> 
> We are getting this error in about every half hour or so:
> 
> java.lang.NullPointerException
> Nov 30, 2011 3:21:28 PM org.apache.tomcat.jdbc.pool.ConnectionPool abandon
> WARNING: Connection has been abandoned PooledConnection[net.sourceforge.jtds.jdbc.ConnectionJDBC3@40c65cd4]:java.lang.E\
> xception
>        at org.apache.tomcat.jdbc.pool.ConnectionPool.getThreadDump(ConnectionPool.java:973)
>        at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:727)
>        at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:585)
>        at org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(ConnectionPool.java:174)
>        at org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(DataSourceProxy.java:124)
>        at pathology.connection.CopathDbInterface.getConnectionFromPull(CopathDbInterface.java:119)
>        at pathology.connection.CopathDbInterface.getConnection(CopathDbInterface.java:85)
>        at pathology.connection.CopathDbInterface.getConnection(CopathDbInterface.java:68)
>        at pathology.histology.server.DashboardServiceImpl.getBlockDashboardStatsMap(DashboardServiceImpl.java:923)
>        at pathology.histology.server.DashboardServiceImpl.getBlockDashboardStats(DashboardServiceImpl.java:513)
>        at pathology.histology.server.DashboardServiceImpl.getDashboardStats(DashboardServiceImpl.java:62)
>        at sun.reflect.GeneratedMethodAccessor597.invoke(Unknown Source)
>        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:597)
>        at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:569)
>        at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:208)
>        at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:248)
>        at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
>        at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
>        at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>        at org.apach
> 
> 
> Any good idea where to start troubleshooting ?

The background pool monitor job is finding connections that either
weren't returned to the pool or have died somehow.  The time it runs is
configurable.

Check your code for try-catch-finally bugs where the connection can
leak, if an uncaught error escapes.

Note: I have rarely had a good experience when dealing with the jTDS
drivers.


p


> Thanks ahead,
> 
> János
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 


-- 

[key:62590808]


Mime
View raw message