https://issues.apache.org/bugzilla/show_bug.cgi?id=25060
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #7 from Mark Thomas <ma...@apache.org> 2011-03-08 17:20:28 EST ---
A LifecycleListener isn't necessarily the best place for this and it would
require explicit configuration.
I have added some clean-up for DataSource resources when naming resources are
stopped but this is far from a generic solution for all resources (and neither
is it meant to be). As Remy points out what is needed is a standard interface
for releasing JNDI resources. DataSources are sufficiently widely used and the
issues sufficiently problematic that I think it makes sense to address them.
The clean-up has been added to Tomcat 7 and will be included in 7.0.11 onwards.
Regarding the thread leak with Commons DBCP, that is a Commons DBCP bug
although one that might be hard to fix.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
