> "Caldarale, Charles R" <chuck.caldar...@unisys.com> wrote in message > news:0aae5ab84b013e45a7b61cb66943c17215b600c...@usea-exch7.na.uis.unisys.com... > > From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric B. > > Subject: dbcp pool freezing > > > > and see that all my threads are in the WAITING state from > > org.apache.tomcat.dbcp.pool.impl.GenericObjectPool.borrowObject > > (GenericObjectPool.java:810) > > > > I don't believe I have any connection leaks in my code > > Belief is not a substitute for evidence... Your webapp is clearly not > returning connection objects to the pool in a timely fashion.
I am tempted to agree with you; I just am having trouble understanding how or why they aren't being returned properly. > > I would expect that if some threads are "busy" doing > > nothing, that they would be cleaned up by the removeAbandoned > > option, and released to the next available thread. > > That's not the way it works. Any connection objects not returned to the > pool in the specified amount of time are simply discarded and new ones > created to take their place. Even better. Then the question becomes why aren't they being returned at all? My timeout is 20secs; I would expect, if the Abandon tracking was working properly for me, that the connections would be returned after 20secs to the pool, and another thread would be able to continue using it. However, this doesn't seem to happen; no threads seem to be returned to the pool and instead, everything just hangs in the WAITING state. Thanks, Eric --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
