Hey all! I am running Jasig cas 3.4.12 with jdbc support and JPA ticket registration. I have noticed that when stopping the Cas application through tomcat it logs to catalina.out the following output:
2012-06-18 09:19:38,371 INFO [org.jasig.cas.util. AutowiringSchedulerFactoryBean] - <Shutting down Quartz Scheduler> Jun 18, 2012 9:19:38 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: The web application [/cas] registered the JBDC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. Jun 18, 2012 9:19:38 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/cas] appears to have started a thread named [Thread-17] but has failed to stop it. This is very likely to create a memory leak. Jun 18, 2012 9:19:38 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/cas] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak. Jun 18, 2012 9:19:38 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/cas] appears to have started a thread named [scheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak. Jun 18, 2012 9:19:38 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/cas] appears to have started a thread named [scheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak. Jun 18, 2012 9:19:38 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/cas] appears to have started a thread named [scheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak. Jun 18, 2012 9:19:38 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/cas] appears to have started a thread named [scheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak. Jun 18, 2012 9:19:38 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/cas] appears to have started a thread named [scheduler_Worker-5] but has failed to stop it. This is very likely to create a memory leak. Jun 18, 2012 9:19:38 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/cas] appears to have started a thread named [scheduler_Worker-6] but has failed to stop it. This is very likely to create a memory leak. Jun 18, 2012 9:19:38 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/cas] appears to have started a thread named [scheduler_Worker-7] but has failed to stop it. This is very likely to create a memory leak. Jun 18, 2012 9:19:38 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/cas] appears to have started a thread named [scheduler_Worker-8] but has failed to stop it. This is very likely to create a memory leak. Jun 18, 2012 9:19:38 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/cas] appears to have started a thread named [scheduler_Worker-9] but has failed to stop it. This is very likely to create a memory leak. Jun 18, 2012 9:19:38 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/cas] appears to have started a thread named [scheduler_Worker-10] but has failed to stop it. This is very likely to create a memory leak. log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository. Is that a known issue? any suggestions? I did noticed that after few stops/starts tomcat memory allocation is growing high and the cpu of the machine is raising up to 99% of usage. Thank! -- * Ronen Itkin* Taykey | www.taykey.com -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
