tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 49667] JdbcLeakPrevention class can register unregistered JCBC Driver
Date Wed, 25 Aug 2010 11:37:23 GMT

--- Comment #3 from Arjen Knibbe <> 2010-08-25 07:37:16
EDT ---
Created an attachment (id=25935)
 --> (
Demo for bug 49667

This tar/zip contains a minimal implementation of the A application as
mentioned in the bug Overview. Application B will follow. Both applications
contain the MySQL JdbC jar file. A pplication A loads the Driver on startup, B
doesn' t.

Starting with a clean Tomcat (no entries in webapps), the bug can be reproduces
as follows:
* copy A.war into webapps, wait until catalina.out shows application A
* copy B.war into webapps, wait until catalina.out shows application B
* Remove B.war from webapps, wait until catalina.out shows context /B
undeployed. Verify that no warning is issued about a Driver being forcilbly
* Optionally, wait an hour.
* Trigger a memory dump using jmap, inspect the dump using jhat.
* in the All Classes excluding plathform screen, verify that class
com.snt.connect.demo.B.servlet.Servlet is still there.
* Click on the class, then click on its class loader.
* Click on Other Queries/Exclude weak refs, verify that class
java.sql.DriverManager is in the System class references, and that class
com.mysql.jdbc.Driver is in that reference chain.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message