Re: using clearReferencesStopTimerThreads value for context

2012-06-27 Thread Mark Thomas
On 27/06/2012 03:04, Supun Malinga wrote: Hi all, Say I have a webapp that don't stop all the timer threads it started upon the webapp undeploy/stop. So tomcat prints an error, The web application [/NewStratosDBAccessServlet] appears to have started a thread named [MySQL Statement

Re: using clearReferencesStopTimerThreads value for context

2012-06-27 Thread Supun Malinga
Hi, On Wed, Jun 27, 2012 at 1:42 PM, Mark Thomas ma...@apache.org wrote: On 27/06/2012 03:04, Supun Malinga wrote: Hi all, Say I have a webapp that don't stop all the timer threads it started upon the webapp undeploy/stop. So tomcat prints an error, The web application

Re: using clearReferencesStopTimerThreads value for context

2012-06-27 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark, On 6/27/12 4:12 AM, Mark Thomas wrote: Getting rid of that message is simple. Fix the bug in the web application. +1 FWIW, Oracle/MySQL says that this bug has been fixed in Connector/J 5.1.11 (http://bugs.mysql.com/bug.php?id=36565). If you

using clearReferencesStopTimerThreads value for context

2012-06-26 Thread Supun Malinga
Hi all, Say I have a webapp that don't stop all the timer threads it started upon the webapp undeploy/stop. So tomcat prints an error, The web application [/NewStratosDBAccessServlet] appears to have started a thread named [MySQL Statement Cancellation Timer] but has failed to stop it. This is