https://issues.apache.org/bugzilla/show_bug.cgi?id=49667
--- Comment #3 from Arjen Knibbe <arjencornelis.kni...@getronics.com> 2010-08-25 07:37:16 EDT --- Created an attachment (id=25935) --> (https://issues.apache.org/bugzilla/attachment.cgi?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 deployed. * copy B.war into webapps, wait until catalina.out shows application B deployed. * Remove B.war from webapps, wait until catalina.out shows context /B undeployed. Verify that no warning is issued about a Driver being forcilbly unloaded. * 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: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
