CODEWITHSUNDEEP
javaloggingdroolsjbpmlog4j2
Pantelis Natsiavas
Pantelis Natsiavas

Reputation: 5369

Log4j 2 - Deactivate drools logger

I am using Log4j 2 and I am unsuccessfully trying to change the logging level of jBPM/Drools, having it as a reference. The drools class that keeps logging is ExtensibleXmlParser. 

<?xml version="1.0" encoding="UTF-8"?>
<Configuration>
    <Appenders>
        <Console name="Console" target="SYSTEM_OUT">
            <PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n" />
        </Console>
    </Appenders>
    <Loggers>
        <Root level="debug">
            <AppenderRef ref="Console" />
        </Root>
        <Logger name="org.drools.core.xml.ExtensibleXmlParser" level="off">
            <AppenderRef ref="Console" />
        </Logger>
    </Loggers>
</Configuration>

If I get it right, ExtensibleXmlParser uses slf4j and Log4j is compatible with sl4j.

Why doesn't this Log4j configuration work? Could someone provide me a working configuration? Should I configure jBPM/Drools logger indendently?

Upvotes: 1

Views: 2053

Answers (1)

MaDa
MaDa

Reputation: 10762

When log4j seems to ignore your tweaks to the log4j.properties/xml file, it most often means you're not fiddling with the right file. It is likely that there is another configuration file in your classpath that gets found earlier and is taken into account.

Search your entire classpath for log4j* pattern and see what comes out (include the contents of .jar files and application server /lib and /ext folders, if any).

If I get it right, ExtensibleXmlParser uses slf4j and Log4j is compatible with sl4j.

"Is compatible" is not equivalent with "is configured to use". SLF4J plugs into appropriate logging framework through the org.slf4j.impl.StaticLoggerBinder class. Search the classpath (best in your IDE) to see what library this class came with. If there is no such class, then SLF4J logs nothing.

Upvotes: 1

Related Questions