tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 37262] - JDBC datasources are never released
Date Thu, 27 Oct 2005 13:47:16 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37262>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37262


bc4all@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |




------- Additional Comments From bc4all@gmail.com  2005-10-27 15:47 -------
While it might not seem elegant to introduce DBCP specific code, it is the
responsibility of the container to close its MANAGED resources. DBCP has no way
of knowing that the tomcat context is  stopped and the pooled connections must
be closed.

An elegant solution would be (as JBoss does) to wrap the resources in a tomcat
class that listens to lifecycle events of the context and calls DBCP to close
the pooled connections when the context is stopped.

I've reopened the bug just so that others can see my comment. Feel free to close
it again, but I think DB connections leaks are a pretty serious.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message