[jira] [Commented] (LOG4NET-583) RolingFileAppender+InterProcessLock is locked after rolling log files

[ https://issues.apache.org/jira/browse/LOG4NET-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337041#comment-17337041 ] Bruno commented on LOG4NET-583: --- Please try my fix at https://github.com/apache/logging-lo

[GitHub] [logging-log4net] brunom opened a new pull request #74: Fix InterProcessLock deadlock

brunom opened a new pull request #74: URL: https://github.com/apache/logging-log4net/pull/74 As discussed in https://issues.apache.org/jira/browse/LOG4NET-583 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL ab

[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #486: LOG4J2-2965: Fix JUL/AsyncLoggerContext deadlock

carterkozak commented on a change in pull request #486: URL: https://github.com/apache/logging-log4j2/pull/486#discussion_r623415612 ## File path: src/changes/changes.xml ## @@ -75,6 +75,9 @@ Slf4j implementations walk the stack at most once rather than twice t

[GitHub] [logging-log4j2] carterkozak opened a new pull request #486: LOG4J2-2965: Fix JUL/AsyncLoggerContext deadlock

carterkozak opened a new pull request #486: URL: https://github.com/apache/logging-log4j2/pull/486 -- 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

[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=17335751#comment-17335751 ] Carter Kozak commented on LOG4J2-2965: -- I'll upgrade disruptor shortly and close th