Re: Stopping a Timer in contextDestroyed() to avoid memory leaks results in a NullPointerException

2010-05-26 Thread Emeric Vernat
IGNED MESSAGE- Hash: SHA1 Emeric, On 5/26/2010 3:52 PM, Emeric Vernat wrote: You could also eliminate the mix& match and add a finally, with the following servlet code for example: public void init() throws ServletException { boolean initOk = false; mytimer =

Re: Stopping a Timer in contextDestroyed() to avoid memory leaks results in a NullPointerException

2010-05-26 Thread Emeric Vernat
Hi, You could also eliminate the mix & match and add a finally, with the following servlet code for example: public void init() throws ServletException { boolean initOk = false; mytimer = new Timer("__test__"); try { TimerT

Re: Javamelody

2010-05-24 Thread Emeric Vernat
Hi Ozgur and others, Ok, I am here. Thanks for the issue about this log. I have tomcat 6.0.26 but I have not reproduced the issue yet. Yes there is a timer thread in javamelody, and it is correctly canceled in the destroy method as can be seen here in the http filter: http://code.google.com/p/