Type: New Feature
Affects Version/s: None
Fix Version/s: 2.0
Lately we got the following exception
org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool exhausted
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().