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=29867>. 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=29867 jdbc database Connecting pool leak [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2004-08-30 20:41 ------- This won't be fixed in Tomcat 5.0.x. You should put the data source in the <Context> proper, not in <DefaultContext>. To manually close the DataSource and/or its connections, do the normal JNDI lookup for it, e.g. InitialContext ictx = new InitialContext(); DataSource ds = (DataSource) ictx.lookup("java:comp/env/jdbc/AdminDB"); Then cast to the DBCP-specific class, org.apache.commons.dbcp.BasicDataSource: BasicDataSource bds = (BasicDataSource) ds; And call bds.close(). If you have trouble with the above or in general, please use the tomcat-user mailing list to ask for help and discuss solutions. Only post proven bugs with test cases to Bugzilla please. Thank you ;) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
