You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/08/21 16:25:15 UTC

DO NOT REPLY [Bug 22625] New: - Removing a webapp(context) doesn't close its datasources(resource)

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=22625>.
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=22625

Removing a webapp(context) doesn't close its datasources(resource)

           Summary: Removing a webapp(context) doesn't close its
                    datasources(resource)
           Product: Tomcat 4
           Version: Nightly Build
          Platform: All
               URL: http://issues.apache.org/bugzilla/show_bug.cgi?id=21182
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: dirk.verbeeck@pandora.be


Move issue from commons-dbcp to tomcat
------------------------------------------------------------
[dbcp] removing a webapp does not force connections closed
http://issues.apache.org/bugzilla/show_bug.cgi?id=21182 
------------------------------------------------------------
Description:
as reported by Michael Holly and Tony Locke on commons-user@jakarta.apache.org
"removing" a Tomcat webapp does not force connections present in DBCP pool be
closed.

In fact even if the webapp is unloaded and dbcp is unloaded 
there is nobody to call BasicDataSource.close()