Edit Question - KnowledgeHub

Title Body

I'm using dbcp connection pooling in tomcat (version 7) and I have a connection leak somewhere in my code. After a short amount of time, a request for a new connection returns the following exception: "Cannot get a connection, pool error Timeout waiting for idle object" I went back through my code and to me it looks like all connections are being closed properly (doesn't everyone say this...). In order to debug this I added the following properties in context.xml: logAbandoned="true" removeAbandoned="true" removeAbandonedTimeout="300" So the resource tag now looks like this: <Resource name="jdbc/findata" auth="Container" type="javax.sql.DataSource" maxActive="20" maxIdle="5" maxWait="10000" username="root" password="xxxxxx" driverClassName="com.mysql.jdbc.Driver" logAbandoned="true" removeAbandoned="true" removeAbandonedTimeout="300" url="jdbc:mysql://localhost:3306/findata"/> I then restarted tomcat and started hitting web pages until the error message appeared (in the browser window). However I haven't yet been able to figure out where the "logAbandoned" property is writing its information. I'm looking in /usr/share/apache-tomcat-7.0.11/logs but the only recently modified log file in there is localhost_access_log.2011-04-18.txt Any assistance is much appreciated.

Tags (comma-separated) Cancel