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 ------- Additional Comments From [EMAIL PROTECTED] 2005-10-27 17:54 ------- (In reply to comment #7) > If the Tomcat team decides that DBCP is a "proprietary" external library that > does not deserve proper integration and furthermore connections leaks are > something totally acceptable, than the documentation at > http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html > should be updated to reflect this position. Funny enough, the doc guides the > users how not to leak connections, but when tomcat does it, it's OK :-( Hmmm...is the responsibility of Tomcat to just release DBCP when it is no longer needed (by any webapp it is hosting), or DBCP's connections as well when just one webapp no longer needs it? Interesting question--the latter may be too granular for it. At any rate, please check the Servlet 2.4 Specification, the very small section SRV.10.2.2 -- for the example given, it appears to indicate that the Developer (that's you ;) should create a servlet context listener class in order to close database connection(s). If so, the only issue appears to be then, does Tomcat give you access to the DBCP object(s) necessary to do such connection closing? Glen -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
