Well, I've tried Mark's code earlier, albeit without using a properties file for Log4J, and the position has improved slightly.
The log indicates the following: INFO: Pausing Coyote AJP/1.3 on ajp-8009 Job Job1 unsubmitted at 2010-10-19 15:18:10 24047 [main] INFO org.quartz.core.QuartzScheduler - Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down. 24047 [main] INFO org.quartz.core.QuartzScheduler - Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused. 24047 [main] INFO org.quartz.core.QuartzScheduler - Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete. Shutting down scheduler 19-Oct-2010 15:18:10 org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina 19-Oct-2010 15:18:10 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application appears to have started a thread named [DefaultQuartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak. 19-Oct-2010 15:18:10 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application appears to have started a thread named [DefaultQuartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak. 19-Oct-2010 15:18:10 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application appears to have started a thread named [DefaultQuartzScheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak. 19-Oct-2010 15:18:10 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application appears to have started a thread named [DefaultQuartzScheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak. 19-Oct-2010 15:18:10 org.apache.coyote.http11.Http11AprProtocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8084 19-Oct-2010 15:18:10 org.apache.coyote.ajp.AjpAprProtocol destroy INFO: Stopping Coyote AJP/1.3 on ajp-8009 Where there are fewer messages but it still seems as if Tomcat is detecting Quartz threads after Quartz is shut down. So my simple question becomes: do these messages matter if Tomcat is restarted or if the host server (which starts Tomcat as a Windows service) is rebooted? -- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
