Track callers of active connections for debugging
-------------------------------------------------
Key: DBCP-229
URL: https://issues.apache.org/jira/browse/DBCP-229
Project: Commons Dbcp
Issue Type: New Feature
Reporter: Armin Häberling
Lately we got the following exception
org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool
exhausted
at
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:103)
at
org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540)
The reason for that was that some piece of code opened a connection, but never
closed it. Tracking the active connections (and the callers of the
getConnection method) would it make it easier to find such erroneous code.
One possible approach would be to add the connection returned by
BasicDataSource.getConnection together with the stacktrace in a Map holding all
active connections. And removing the connection from the map during
PoolableDataSource.close().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
