Remko Popma created LOG4J2-1164:
-----------------------------------
Summary: Configuration watch thread causes Tomcat memory leak
Key: LOG4J2-1164
URL: https://issues.apache.org/jira/browse/LOG4J2-1164
Project: Log4j 2
Issue Type: Bug
Components: Configurators
Affects Versions: 2.5
Reporter: Remko Popma
While investigating LOG4J2-1159 I found that Tomcat (7.0.50) now gives this
output when I shut it down while the test webapp is deployed:
{noformat}
SEVERE: The web application [/threadlocal] appears to have started a thread
named [pool-2-thread-1] but has failed to stop it. This is very likely to
create a memory leak.
{noformat}
This thread is probably the ScheduledExecutor that is now started if
monitorInterval > 0. Still checking why the app is not stopped() and the
executor is not shut down...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
