Thanks for this. I've copied the logs over to an incident in Quartz's forum so hopefully, I can get to the bottom of this issue.
http://forums.terracotta.org/forums/posts/list/4341.page -----Original Message----- From: Pid [mailto:p...@pidster.com] Sent: 20 Oct 2010 16 37 To: Tomcat Users List Subject: Re: Tomcat memory leak error launching web app in NetBeans 6.9.1 On 20/10/2010 12:41, Martin O'Shea wrote: > And then when I terminate the Quartz application, but leave Tomcat > running, the second dump appears to be show no trace of these messages > at all. So does this indicate that Quartz has shut down but only after > my application has stopped within Tomcat, i.e. that Tomcat monitors my > application's demise and reports the threads as extant because Quartz has not yet ended? The memory leak detection activates when a web app stops. The question is whether the Quartz scheduler blocks and waits for its worker threads to finish before it reports that it's shutdown. I don't believe it does, which isn't your fault. p --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
