This may be caused by the LoggerContext.stop() method not being called. Which version of Tomcat are you using? Special care is needed for Tomcat 7.0.40 and older.
A similar issue, LOG4J2-578 seemed to be caused by a config issue where the version number in web.xml was incorrect. Can you check this? Also, are the log4j jars under the shared Catalina lib? I suspect the problem goes away if you put the log4j jars under your webapp's WEB-INF/lib folder. Remko Sent from my iPhone > On 2014/04/10, at 11:24, Mahesh Dilhan <[email protected]> wrote: > > HI > > I got following catalina console out continuously when I try to stop the > web application. > > Brief on configuration > *version : rc1* > > *Log4j2.xml* > > <Configuration status="OFF" > > <Appenders> > <RollingRandomAccessFile name="RollingFile-${web:contextPath}" > fileName="${sys:catalina.home}/logs/current/${web:contextPath}.log" > immediateFlush="false" append="false" > > filePattern="${sys:catalina.home}/logs/archived/%d{yyyy-MM-dd}${contextName}-%d{yyyy-MM-dd}.log.gz"> > <PatternLayout> > <Pattern>%d %p %c{1.} [%t] %m%n</Pattern> > </PatternLayout> > <Policies> > <TimeBasedTriggeringPolicy /> > </Policies> > </RollingRandomAccessFile> > </Appenders> > <Loggers> > <Root level="INFO" includeLocation="false"> > <AppenderRef ref="RollingFile-${web:contextPath}"/> > > </Root> > </Loggers> > </Configuration> > > *Tomcat properties :* > Asysnc logger [tomcat is configured with the property > {Log4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector > } > > > > > > Apr 08, 2014 12:32:17 PM org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads > 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 > checkThreadLocalMapForLeaks > 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 ? > > > Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
