ppkarwasz commented on issue #3579: URL: https://github.com/apache/logging-log4j2/issues/3579#issuecomment-2757231370
@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](https://logging.apache.org/log4j/2.x/manual/architecture.html#LoggerContext) 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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
