logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Wehner (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LOG4J2-945) Reconfiguring statusLogger to a higher level doesn't work correctly
Date Wed, 28 Jan 2015 11:40:34 GMT
Stefan Wehner created LOG4J2-945:

             Summary: Reconfiguring statusLogger to a higher level doesn't work correctly
                 Key: LOG4J2-945
                 URL: https://issues.apache.org/jira/browse/LOG4J2-945
             Project: Log4j 2
          Issue Type: Bug
          Components: Core
    Affects Versions: 2.1
            Reporter: Stefan Wehner
            Priority: Minor

When reconfiguring log4j and changing the level of the status logger to a higher level - e.g.
from WARN to DEBUG, it doesn't work correctly.

Steps to reproduce:
# Configure from log4j2.xml containing:
<Configuration status="WARN" monitorInterval="5">
# With the app running, change status to a higher level:
<Configuration status="DEBUG" monitorInterval="5">
# Observe that the log config is reloaded, but no debug messages for the status logger appear.

>From what I've seen this is because the StatusConfig.initialize() reconfigures the listeners'

But it doesn't update the listenersLevel field that the StatusLogger uses for checking if
the logger is enabled (I understand this should be the maximum of all of the listener's levels)


So in this case the listenersLevel is still at WARN, even though the console listener has
a DEBUG level, and all the log messages are ignored because isEnabled(DEBUG) returns false.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message