DO NOT REPLY [Bug 18615] New: - connectionpool loses reference to connections

[bu...@apache.org]

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

connectionpool loses reference to connections

           Summary: connectionpool loses reference to connections
           Product: Tomcat 4
           Version: 4.1.18
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: sal_cheung@yahoo.com


When a class or jar file is replaced for a running web application,
tomcat reloads class files, it also reinitialize
the context and the connection pool.  But if there are
users hitting the site and prob. still using the connections, 
the connections dont get
closed property. These connections still connect to
the DB server, but can no longer be referenced in the newly intialized
connection pool.

These connections don't get released unless tomcat server is restarted.

This bug can be reproduced by replacing a jar file or a class file in the web 
application that is actively accessed by multiple users.

One can see the lost db connections by comparing the total number of 
connections in connection pool with the number of db connections opened from 
tomcat server to the db server(netstat -a |grep dbPortNumber will do the trick)

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