StatusLogger `dest=file.log` property creates an empty file

[voddan]

Description

I specified <Configuration dest="file.log"> in my log4j2.xml.
I expected the status logger messages to be redirected to that file. Instead the file.log was created, but it remained empty, and all the status logging messages were printed to console as before.

Configuration

Version: 2.24.3

Operating system: Windows 11

JDK: Amazon Correto 17.0.12

Reproduction

1. Specify <Configuration dest="file.log"> in log4j2.xml.
2. file.log is created, but is empty
3. Status logs are still in the console

[ppkarwasz]

@voddan,

I am unable to reproduce the problem with the steps you provided. Can you provide a minimal reproducible example? Can you provide the logs of the initialization procedure of Log4j Core? Setting -Dlog4j2.statusLoggerLevel=INFO should be enough to see the lifecycle of the configurations for all your logger contexts.

Note

Using the dest attribute in a configuration file should be considered deprecated: StatusLogger is a global resource shared by all the logger contexts in your system.
Each configuration will reconfigure StatusLogger when it starts. This is why we don't recommend using neither the status nor the dest configuration attributes.

You question about StatusListener (#3576) provides a better way to redirect status logs to a file. I'll follow up on that.

[github-actions]

This issue is stale because it has been waiting for your feedback for more than 60 days. The Apache Logging Services community values every submitted issue, but without additional information from you, we are unable to provide a solution to your problem.
Please comment on this issue or it will be closed in 7 days.