-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark,
On 7/20/2011 4:25 AM, Mark Thomas wrote: > You need to de-register the driver you registered. However, that > won't be causing the leak since Tomcat already did the clean up for > you. Time to get the profiler out. Quick question: I get these JDBC Driver messages from Tomcat when I undeploy, but my code does not register the driver itself... Tomcat does via a <Resource> defined in context.xml. Is that driver registered with the WebappClassLoader and therefore considered "registered" by the webapp? I've been irritated by this behavior for a while because I feel like the container is performing the registration of the driver, but expecting the webapp to perform the de-registration. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4nPr8ACgkQ9CaO5/Lv0PCtawCglncNAXh36PhsbX7RumBEY7UK 8OgAni40dlStbgDSEtskmROivDqPvO0b =9j/G -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
