Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
1.1.3
-
None
-
SUSE LINUX Enterprise Server 9 (i586)(Patchversion: 9.4) - Linux version 2.6.5-7.312-bigsmp (32Bit)
-
Patch
Description
It looks like the Quartz thread is still running because the web-context has been unloaded before.
This could maybe happen because the Quartz threads are not yet under Spring control (http://jira.springframework.org/browse/SPR-5065).
Exception summary :
INFO: Illegal access: this web application instance has been stopped already. Could not load org.quartz.StatefulJob. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1273)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at org.quartz.JobDetail.class$(JobDetail.java:59)
at org.quartz.JobDetail.isStateful(JobDetail.java:396)
at org.quartz.simpl.RAMJobStore.triggerFired(RAMJobStore.java:1207)
at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:307)
Exception in thread "defaultScheduler_QuartzSchedulerThread" java.lang.NoClassDefFoundError: org.quartz.StatefulJob