Hello We are running CAS on RHEL6. We have found that if we replace the cas.war file w/o stopping tomcat and then restarting it, a memory leak is thrown because others threads are not cleared. The following is a typical log message:
INFO: Stopping service Catalina Feb 26, 2014 1:49:10 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: A web application registered the JBDC driver [oracle.jdbc.driver.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. Feb 26, 2014 1:49:10 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak. Feb 26, 2014 1:49:10 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. Feb 26, 2014 1:49:10 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. - Does anyone else have this issue? - To anyone's knowledge, is it specific to RHEL6? - Does anyone know where the memory leaks occurs, modified the CAS source and rebuilt the jar for it? Linda -- Linda Toth University of Alaska - Office of Information Technology (OIT) - Identity and Access Management 910 Yukon Drive, Suite 103 Fairbanks, Alaska 99775 Tel: 907-450-8320 Fax: 907-450-8381 [email protected] | www.alaska.edu/oit/ -- 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
