Environment:
Windows 10 Pro
Oracle Java 1.8.0_74
Tomcat 8.0.24
jython-standalone 2.7.0
Camunda Community edition 7.4.0
When using a Jython script inside a Camunda BPMN process, I can no longer do a live redeploy of the Camunda webapp. Upon live redeployment, I got the following SEVERE message from Tomcat:
20-Apr-2016 09:42:08.151 SEVERE [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [loan-approval-0.0.1-SNAPSHOT] created a ThreadLocal with key of type [org.python.core.ThreadStateMapping$1] (value [org.python.core.ThreadStateMapping$1@3900df7d]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@719437fb]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
And after this message, Tomcat also log the following:
20-Apr-2016 09:42:08.151 SEVERE [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [loan-approval-0.0.1-SNAPSHOT] created a ThreadLocal with key of type [org.python.core.ThreadStateMapping$1] (value [org.python.core.ThreadStateMapping$1@3900df7d]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@719437fb]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
This leaves the webapp in an unusable state and we have to shutdown Tomcat in order to be able to use the BPMN process application again. |
