commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DBCP-229) Track callers of active connections for debugging
Date Mon, 15 Feb 2010 04:27:28 GMT

     [ https://issues.apache.org/jira/browse/DBCP-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Phil Steitz updated DBCP-229:
-----------------------------

    Fix Version/s:     (was: 1.4)
                   2.0

> 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
>             Fix For: 2.0
>
>
> 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.


Mime
View raw message