Self-Solve Knowledge Search

Minimize Maximize
SEVERE log messages in wrapper.log of Central indicating a memory leak
Title :
SEVERE log messages in wrapper.log of Central indicating a memory leak
Document ID :
KM01368633
Product - Version:
operations orchestration 10.00 10.10 ;
OS :
Updated :
Mon Jan 26 06:56:23 GMT 2015
Summary :
SEVERE log messages in wrapper.log of Central indicating a potential memory leak can be ignored.

When trying to stop Central service, even if it succeeds, the following SEVERE log messages indicating a potential memory leak are recoded in Central's wrapper.log:

  INFO   | jvm 2    | 2015/MM/DD 14:25:51 | MMM DD, 2015 2:25:51 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
  INFO   | jvm 2    | 2015/MM/DD 14:25:51 | SEVERE: The web application [/oo] appears to have started a thread named [<CLASSNAME>] but has failed to stop it. This is very likely to create a memory leak.

  INFO   | jvm 2    | 2015/MM/DD 14:25:52 | MMM DD, 2015 2:25:51 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
  INFO   | jvm 2    | 2015/MM/DD 14:25:52 | SEVERE: The web application [/oo] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@2e34dac3]) and a value of type [<CLASSNAME>] (value [<CLASSNAME>@ffffffff: Null authentication]) 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 any way to get rid of the messages? Can they be ignored?

Solution
Currently there is no way provided by OO to prevent those messages and they can be ignored.