ppkarwasz commented on issue #2258: URL: https://github.com/apache/logging-log4j2/issues/2258#issuecomment-1921256723
No, it is async. When we talk about async loggers, we are actually talking about two **different** implementations: - [`AsyncLogger`](https://logging.apache.org/log4j/2.x/javadoc/log4j-core/org/apache/logging/log4j/core/async/AsyncLogger.html) is what we refer in the docs as [full async logger configuration](https://logging.apache.org/log4j/2.x/manual/async.html#making-all-loggers-asynchronous). The Disruptor starts **before** your configuration is read, so you don't see it in the logs. You need to set `-Dlog4j2.debug` to see the messages. This is the **fastest** (cf. [somehow dated benchmarks](https://logging.apache.org/log4j/2.x/manual/async.html#asynchronous-logging-performance)) of the two, - [`AsyncLoggerConfig`](https://logging.apache.org/log4j/2.x/javadoc/log4j-core/org/apache/logging/log4j/core/async/AsyncLoggerConfig.html) is what we refer in the docs as [mixed async logger configuration](https://logging.apache.org/log4j/2.x/manual/async.html#mixing-synchronous-and-asynchronous-loggers). This is your **initial** configuration. The implementation is much more complex to allow both sync and async logging, hence it is slower and it is easier to find bugs in it. Thanks for confirming that the reported bug does not concern `AsyncLogger`, but only `AsyncLoggerConfig`. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
