DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25060>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25060 Reloading context orphans currently open jndi datasource connections ------- Additional Comments From [EMAIL PROTECTED] 2003-12-07 17:34 ------- Yes, it may be that when the JNDI resource is defined within a Context and the context is reloaded or stopped, the previous JNDI objects may still consume their resources including db connections until they are GC'd. At a minimum we need to verify whether the already existing resources become eligible for GC after a reload/stop of a Context and there is no memory/resource leak. Even if there is no memory leak and the previous JNDI DataSource becomes eligible for GC it might be nice to explicitly close the db connections. If the DBCP DataSource is being used a possible solution to free up resources would be a Context LifeCycle Listener that does a close on the DBCP DataSource during a Context reload/stop. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
