| Servet bridge: tomcat severe logs about possible memory leak [message #1777851] |
Tue, 05 December 2017 10:18  |
 Arnaud MERGEY
Messages: 243
Registered: March 2010
Location: France |
Senior Member |
|
|
Hello,
Stopping an application built on top of servlet bridge, deployed on tomcat 8.5
I can find these SEVERE level logs
SEVERE [http-nio-8088-exec-3] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [app] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@473cab84]) and a value of type [org.eclipse.osgi.internal.loader.classpath.ClasspathManager.DefineContext] (value [org.eclipse.osgi.internal.loader.classpath.ClasspathManager$DefineContext@7ade541c]) 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.
Even I am pretty sure tomcat is managing this so there is no really a memory leak, but having something SEVERE in logging is not really cleaned.
Also clicking on leak detector on tomcat manager give this
05-Dec-2017 11:37:44.149 SEVERE [http-nio-8088-exec-13] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [app] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@1179aeb8]) and a value of type [org.eclipse.osgi.internal.weaving.WeavingHookConfigurator.WovenClassContext] (value [org.eclipse.osgi.internal.weaving.WeavingHookConfigurator$WovenClassContext@7b5a8a18]) 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.
Is there something I could do to avoid these ? it seems to me that the cause could be something internal to equinox in servlet bridge.
[Updated on: Tue, 05 December 2017 10:43] Report message to a moderator |
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03835 seconds
] 
Search
Help
Register
Login
Home
