Unwanted logging by StatusLogger

[morvael]

Description

I think after the changes in 4e00ea4 I can now observe logging from org.apache.logging.log4j.core.config.AbstractConfiguration ("Starting configuration...", "Start watching for changes to...", etc) which were previously hidden by default. I think that logger used to by WARN by default, now it's INFO by default.

Configuration

Version: 2.24.1

Operating system: Linux Mint 21.3

JDK: Adoptium 21.0.4+7

[morvael]

The following lines are logged at the start:

Starting configuration XmlConfiguration[location=… , lastModified=…]...
Start watching for changes to … every 0 seconds
Configuration XmlConfiguration[location=… , lastModified=…] started.
Stopping configuration org.apache.logging.log4j.core.config.DefaultConfiguration@…
Configuration org.apache.logging.log4j.core.config.DefaultConfiguration@… stopped.

And these at the end:

Stopping configuration XmlConfiguration[location=… , lastModified=…]...
Configuration XmlConfiguration[location=… , lastModified=…] stopped.

[ppkarwasz]

Hi @morvael,

The default status logger level in version 2.24.1 is still ERROR. Can you check:

1. If your configuration file does not use the deprecated status attribute.
2. If you don't define the deprecated Log4jDefaultStatusLevel, log4j2.defaultStatusLevel or LOG4J_DEFAULT_STATUS_LEVEL properties in a property source (Java System properties, environment variables, log4j2.component.properties file).
3. If you don't define the log4j2.statusLoggerLevel property as Java System property, environment variable or in a log4j2.StatusLogger.properties file.

[morvael]

I will re-verify but I actually tried to use any and all of them to change the log level to WARN and nothing changed, it still printed that INFO.

[morvael]

I have no guarantee though that some of the dependencies I use doesn't do one of those things :(

[vy]

@morvael, could you try putting a breakpoint to the StatusLogger.Config#Config() ctor and see where the incorrect level is sourced from, please?

[morvael]

Will try. For now this is the stack trace when I get first log line: