Re: Timer leak detection, false positives

2010-06-11 Thread Marcus Better
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark Thomas wrote: >> This thread belongs to EhCache, and by inspecting the code, it looks like >> the timer should be cancelled properly when the application is shut down. > Does the app wait for the thread to stop or does it just cary on? It doesn'

Re: Timer leak detection, false positives

2010-06-11 Thread Mark Thomas
On 11/06/2010 14:13, Marcus Better wrote: > Hi, > > I run a Grails app on Tomcat 6.0.26 (OpenJDK 6, Debian). When undeploying, > it reports several leaked objects, including a timer thread that was left > running. > > This thread belongs to EhCache, and by inspecting the code, it looks like >

Re: Timer leak detection, false positives

2010-06-11 Thread Pid
On 11/06/2010 14:13, Marcus Better wrote: > Hi, > > I run a Grails app on Tomcat 6.0.26 (OpenJDK 6, Debian). When undeploying, > it reports several leaked objects, including a timer thread that was left > running. > > This thread belongs to EhCache, and by inspecting the code, it looks like > the

Timer leak detection, false positives

2010-06-11 Thread Marcus Better
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I run a Grails app on Tomcat 6.0.26 (OpenJDK 6, Debian). When undeploying, it reports several leaked objects, including a timer thread that was left running. This thread belongs to EhCache, and by inspecting the code, it looks like the timer s