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

Posted to dev@commons.apache.org by bu...@apache.org on 2003/06/30 13:01:54 UTC

DO NOT REPLY [Bug 21182] New: - [dbcp] removing a webapp does not force connections closed

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

[dbcp] removing a webapp does not force connections closed

           Summary: [dbcp] removing a webapp does not force connections
                    closed
           Product: Commons
           Version: 1.0 Alpha
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Dbcp
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: tagunov@motor.ru


as reported by Michael Holly <mh...@talisentech.com> and Tony Locke <tl...@tlocke.org.uk> 
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().

Probably some context listener would 
solve this problem but I fear not to have enough competence to say how to hook it in.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org