[jira] [Commented] (LOG4J2-2965) Deadlock between JUL and Disruptor using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330912#comment-17330912 ] Carter Kozak commented on LOG4J2-2965: -- This issue will be resolved by upgrading to

[GitHub] [logging-log4j2] carterkozak commented on pull request #447: Reproducer JMH benchmark for LOG4J2-2965

carterkozak commented on pull request #447: URL: https://github.com/apache/logging-log4j2/pull/447#issuecomment-825784280 Closing this reproducer out, the next release of disruptor will no longer internally initialize loggers upon creation: https://github.com/LMAX-Exchange/disruptor/issu

[GitHub] [logging-log4j2] carterkozak closed pull request #447: Reproducer JMH benchmark for LOG4J2-2965

carterkozak closed pull request #447: URL: https://github.com/apache/logging-log4j2/pull/447 -- 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. For queries about this servic