: SHA1 > > Filip, > > On 3/28/12 12:00 PM, Filip Hanik (mailing lists) wrote: > > PoolCleaner is a static singleton. The pool cleaner thread will not > > be removed until all JDBC pools have been stopped. So, yes, one > > application can be the one that starts the thread, but not > > necessarily the one that stops it > > Is there any reason not to associate the thread with the > WebappClassLoader's parent? Otherwise, this will pin the first webapp > to use tomcat-pool in memory until all webapps have been undeployed, > right? [Filip Hanik]
Correct, I can add in a fix for this to force the context classloader to be the same as the pool while it is starting the thread > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk9zPQkACgkQ9CaO5/Lv0PD7wwCeOR3bVeJOk6fyWsTtzE3Fp > bzm > Bk8AnjrsNqyp3zsHexJhIuLumEgZ1fsj > =pI1I > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
