Definitely seems to be when the web application in question is terminated, rather than Tomcat itself. And all indications are the listener that handles the scheduler.
And I've tried another similar application which gives messages of the same kind. And yet both apps have worked under other environments. -----Original Message----- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: 16 Oct 2010 15 53 To: Tomcat Users List Subject: RE: Tomcat memory leak error launching web app in NetBeans 6.9.1 > From: Martin O'Shea [mailto:app...@dsl.pipex.com] > Subject: RE: Tomcat memory leak error launching web app in NetBeans 6.9.1 > When the application is terminated, e.g. when the server > is stopped, appropriate messages are issued to confirm > that the scheduler has stopped. What about when it's just the webapp being stopped, not the whole server? Try stopping just the webapp, then take a thread dump of Tomcat to see if the quartz threads are really still there. If they are, then the shutdown logic in the listener isn't working. > And the configuration is the only one on this PC, Tomcat 6.0.26 > using JVM 1.6.0_21-b07. I'm using JDK 1.6.0_21. IDEs have a nasty habit of substituting their own Tomcat and webapp configurations rather than using the ones you think you've set up. You won't find additional Tomcat or JDK installations, just behavior that's not consistent with what you configured. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
