https://issues.apache.org/bugzilla/show_bug.cgi?id=53367
Filip Hanik <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #8 from Filip Hanik <[email protected]> --- I think you may experience a different scenario here, than the actual bug reported. http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java?view=markup Line throw new PoolExhaustedException("[" + Thread.currentThread().getName()+"] " + "Timeout: Pool empty. Unable to fetch a connection in " + (maxWait / 1000) + " seconds, none available[size:"+size.get() +"; busy:"+busy.size()+"; idle:"+idle.size()+"; lastwait:"+timetowait+"]."); The statement busy.size() is not just a counter, it actually measures the number of connections that are placed in the busy queue. Here is what I would do 1. set logAbandoned="true" //this will print a log entry of places in your code that are leaking connections (ie failing to call Connection.close()) With the log output from 1, we should be able to resolve all your problems. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
