--- On Mon, 8/17/09 at 11:38 AM, Kristen Walker <kwal...@sbceo.org> wrote:
> We had some help debugging the connection pool exhausted issue over the > weekend and for now it seems that changing jdbcUsePool=true to > jdbcUsePool=false stops the site from crashing due to connection pool > issues. We are going to investigate more to see why connection pooling > isn't working like expected. You can obtain a stack trace that should point to the offending code by using the Deprecated log abandoned functionality in BasicDataSource: setLogAbandoned() setRemoveAbandoned() setRemoveAbandonedTimeout() http://commons.apache..org/dbcp/apidocs/org/apache/commons/dbcp/BasicDataSource.html There is some indication that logging of abandoned connections/statements will continue in some form: http://wiki.apache.org/commons/DBCP - Bob --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org