[jboss-jira] [JBoss JIRA] (DROOLS-406) Memory Leak during drool workbench deployment on tomcat 7
Mohit Srivastava created DROOLS-406:
---------------------------------------
Summary: Memory Leak during drool workbench deployment on tomcat 7
Key: DROOLS-406
URL: https://issues.jboss.org/browse/DROOLS-406
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.0.1.Final
Environment: OS: Centos 6.5
Reporter: Mohit Srivastava
Assignee: Mark Proctor
After restarting the service fro tomcat manager causes following error:
Jan 18, 2014 8:17:51 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [/drools-wb-6.0.1.Final-tomcat7.0] appears to have started a
thread named [pool-4-thread-1] but has failed to stop it. This is very likely to create a
memory leak.
Jan 18, 2014 8:17:51 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [/drools-wb-6.0.1.Final-tomcat7.0] appears to have started a
thread named [Thread-4] but has failed to stop it. This is very likely to create a memory
leak.
Jan 18, 2014 8:17:51 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [/drools-wb-6.0.1.Final-tomcat7.0] appears to have started a
thread named [pool-7-thread-1] but has failed to stop it. This is very likely to create a
memory leak.
Jan 18, 2014 8:17:51 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [/drools-wb-6.0.1.Final-tomcat7.0] appears to have started a
thread named [com.google.inject.internal.util.$Finalizer] but has failed to stop it. This
is very likely to create a memory leak.
Jan 18, 2014 8:17:51 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [/drools-wb-6.0.1.Final-tomcat7.0] appears to have started a
thread named [Thread-5] but has failed to stop it. This is very likely to create a memory
leak.
Full trace: http://pastebin.com/75tAuZvu
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira