[LOG4J2-945] Reconfiguring statusLogger to a higher level doesn't work correctly

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.1
• Fix Version/s: 2.3
• Component/s: Core
• Assignee: Remko Popma
• Reporter: Stefan Wehner
• Created: 28/Jan/15 11:40
• Updated: 09/Mar/16 21:57
• Resolved: 09/Mar/16 21:57

Description

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:

1. Configure from log4j2.xml containing:

   <Configuration status="WARN" monitorInterval="5">
   ...
   

2. With the app running, change status to a higher level:

   <Configuration status="DEBUG" monitorInterval="5">
   ...
   

3. 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 StatusConfiguration.initialize() reconfigures the listeners' level
StatusConfig:193

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)

StatusLogger:273

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.

Issue Links

• relates to: LOG4J2-947 A new StatusLoggerAdmin listener is added to StatusLogger every time the log is reconfigured