logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mahesh Dilhan <mail.mahesh...@gmail.com>
Subject Catalina.out trace : memory leak
Date Thu, 10 Apr 2014 02:24:48 GMT

I got following catalina console out continuously  when I try to stop the
 web application.

Brief  on configuration
*version : rc1*


<Configuration status="OFF" >
    <RollingRandomAccessFile name="RollingFile-${web:contextPath}"
immediateFlush="false" append="false"

        <Pattern>%d %p %c{1.} [%t] %m%n</Pattern>
        <TimeBasedTriggeringPolicy />
    <Root level="INFO" includeLocation="false">
      <AppenderRef ref="RollingFile-${web:contextPath}"/>


*Tomcat properties :*
 Asysnc logger [tomcat is configured with the property

Apr 08, 2014 12:32:17 PM org.apache.catalina.loader.WebappClassLoader
SEVERE: The web application [/app] appears to have started a thread named
[AsyncLogger-1] but has failed to stop it. *This is very likely to create a
memory leak.*
Apr 08, 2014 12:32:17 PM org.apache.catalina.loader.WebappClassLoader
SEVERE: The web application [/app] created a ThreadLocal with key of type
[java.lang.ThreadLocal] (value [java.lang.ThreadLocal@e8d7057]) and a value
of type [org.apache.logging.log4j.core.async.AsyncLogger.Info] (value
[org.apache.logging.log4j.core.async.AsyncLogger$Info@67ca6737]) 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.

What could be missing in my configuration to run into a such console trace ?
What are the fixes I should look-into ?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message