AnsweredAssumed Answered

Activiti Explorer / Engine causes Tomcat memory leak

Question asked by b.schnarr on Apr 25, 2014
Latest reply on Mar 12, 2015 by babblu
I have deployed the activiti explorer 5.15.1 and when I look into the tomcat loggs, I see this here:


Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-74] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-79] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-84] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-89] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-92] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-95] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-98] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-101] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-103] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-105] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-107] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-110] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-113] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-116] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-121] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-126] but has failed to stop it. This is very likely to create a memory leak.
Apr 24, 2014 11:32:31 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Schwerwiegend: The web application [/activiti-explorer] appears to have started a thread named [Thread-131] but has failed to stop it. This is very likely to create a memory leak.


In addition, you can see this several times even though I use MySQL:


Apr 24, 2014 11:46:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
Schwerwiegend: The web application [/activiti-explorer] registered the JDBC driver [org.h2.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.


Has anyone an idea why this is happen?
Thanks and best regards
Ben

Outcomes