dimitarndimitrov commented on PR #4038: URL: https://github.com/apache/logging-log4j2/pull/4038#issuecomment-3979129078
> Would you mind pushing some changes (e.g., fix a typo 😅, merge changes from upstream/2.x) to get it re-activated, please? Sure, pushed an empty commit, and it looks like it's now waiting for your approval to run again. > There are several ways to achieve this, and they are all covered in [Asynchronous logging](https://logging.apache.org/log4j/2.x/manual/performance.html#async). Have you also experimented with asynchronous appenders? If so, have you also tried [customizing its queue](https://logging.apache.org/log4j/2.x/manual/appenders/delegating.html#BlockingQueueFactory)? No, we haven't tried asynchronous appenders, because their blocking queue component didn't seem to fit our event loop use-case that well. -- 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]
