This is also interesting, the log after a redeploy: Apr 6, 2010 2:04:05 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: A web application 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. Apr 6, 2010 2:04:05 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application appears to have started a thread named [pool-1-thread-1] but has failed to stop it. This is very likely to create a memory leak. Apr 6, 2010 2:04:05 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThread SEVERE: A web application appears to have started a TimerThread named [MySQL Statement Cancellation Timer] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled. [Deprecated] Xalan: org.apache.xml.security.c14n.CanonicalizationException Apr 6, 2010 2:04:06 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive cas.war Apr 6, 2010 2:04:26 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8080 Apr 6, 2010 2:04:26 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8443 Apr 6, 2010 2:04:27 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Apr 6, 2010 2:04:27 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application 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. Apr 6, 2010 2:04:27 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application 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. Apr 6, 2010 2:04:27 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application 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. Apr 6, 2010 2:04:27 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application 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. Apr 6, 2010 2:04:27 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application 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. Apr 6, 2010 2:04:27 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application 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. Apr 6, 2010 2:04:27 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application 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. Apr 6, 2010 2:04:27 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application 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. Apr 6, 2010 2:04:27 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application 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. Apr 6, 2010 2:04:27 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application 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. Apr 6, 2010 2:04:27 PM org.apache.catalina.loader.WebappClassLoader loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load com.mysql.jdbc.SQLError. 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:1402) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1361) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:398) at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3317) at com.mysql.jdbc.MysqlIO.quit(MysqlIO.java:1668) at com.mysql.jdbc.ConnectionImpl.realClose(ConnectionImpl.java:4461) at com.mysql.jdbc.ConnectionImpl.cleanup(ConnectionImpl.java:1359) at com.mysql.jdbc.ConnectionImpl.finalize(ConnectionImpl.java:2809) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83) at java.lang.ref.Finalizer.access$100(Finalizer.java:14) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160) Apr 6, 2010 2:04:27 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080 Apr 6, 2010 2:04:27 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8443
-- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
