Log4J2和Tomee Plus 7.0.47无法正常工作

Question

According to here , Log4j2 should work with Tomcat7.0.47. I'm using TomEE Plus 7.0.47.

I have a webapplication deployed with a log4j2.xml in my web-inf/classes folder. This is the config:

<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="WARN">
<Appenders>
    <Console name="Console" target="SYSTEM_OUT">
        <PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
    </Console>
    <File name="File" fileName="${sys:catalina.home}/logs/testapp.log">
        <PatternLayout>
            <pattern>%d %p %C{1.} [%t] %m%n</pattern>
        </PatternLayout>
    </File>
</Appenders>
<Loggers>
    <Logger name="org.alex" level="TRACE" additivity="false">
        <AppenderRef ref="File"/>
    </Logger>
    <Root level="INFO">
        <AppenderRef ref="Console"/>
    </Root>
</Loggers>
</Configuration>

I have a logger declared in a class with name org.alex.util.JSON:

private static final Logger LOG = LoggerFactory.getLogger(JSON.class);

I'm using slf4j-api 1.7.5, and have the following libs added to the tomcat lib:

• slf4j-api-1.7.5.jar
• log4j-api-2.0-rc1.jar
• log4j-core-2.0-rc1.jar
• log4j-slf4j-impl-2.0-rc1.jar

If I change the Configuration status to TRACE, I can see my configuration file being picked up and configuration happens as expected. Also I can see the MBeans being added. However, there's not one logging statement ending up in my logfile. I debugged into the log4j2 Logger, and see that the isEnabled(...) method returns false because the logger (com.alex.util.JSON) has the level "ERROR" set, while the configuration set the package org.alex to TRACE. Further investigation shows it uses a DefaultConfiguration configured for level=ERROR, and only root is configured. I'm thinking of a classloader issue, but I can't seem to figure out what the cause is and how to solve it. Does anyone know what I'm doing wrong?

Answer 1

This should work on trunk

Btw saw log4j2 has hacks for tomcat and since tomee wraps classloaders not sure they work as expected...

Answer 2

This is very strange. Please raise a ticket for this in the Log4j2 issue tracker so the Log4j team can take a look.

The problem may go away if you put the jar files you mentioned inside WEB-INF/lib instead of in Tomcat's lib folder.

Answer 3

To be comple log4j2 relies on servletcontainerinitializer which are called after ejb and app scanning so ejbs can be loaded too early. Doing the same with a tomcat context listener would make it working better