Bug #62170 | failed to unregister [com.mysql.jdbc.Driver] when stop tomcat posible memory lea | ||
---|---|---|---|
Submitted: | 15 Aug 2011 1:04 | Modified: | 16 Aug 2011 6:36 |
Reporter: | Pedro Figueira | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S5 (Performance) |
Version: | 5.1.17 | OS: | Windows (Apache Tomcat/6.0.32) |
Assigned to: | CPU Architecture: | Any | |
Tags: | Is actually a problem of pool. |
[15 Aug 2011 1:04]
Pedro Figueira
[15 Aug 2011 13:42]
Mark Matthews
JDBC drivers no nothing about Tomcat's lifecycle, therefore they can not know when they may be "unregistered", so this is not a bug in Connector/J. You'll have to either use a connection pool that has been wired into Tomcat's context lifecycle listening framework, or use com.mysql.jdbc.NonRegisteringDriver as the driver you pass to connection pools.
[16 Aug 2011 6:36]
Pedro Figueira
Thank you for the quick response. It is the pool that does not unregister. Again, thank you