30 Sep 11:27
DO NOT REPLY [Bug 45915] New: DeadLock occured in AsyncAppender
From: <bugzilla <at> apache.org>
Subject: DO NOT REPLY [Bug 45915] New: DeadLock occured in AsyncAppender
Newsgroups: gmane.comp.jakarta.log4j.devel
Date: 2008-09-30 09:31:25 GMT
Subject: DO NOT REPLY [Bug 45915] New: DeadLock occured in AsyncAppender
Newsgroups: gmane.comp.jakarta.log4j.devel
Date: 2008-09-30 09:31:25 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=45915 Summary: DeadLock occured in AsyncAppender Product: Log4j Version: 1.2 Platform: HP OS/Version: HP-UX Status: NEW Severity: critical Priority: P2 Component: Appender AssignedTo: log4j-dev <at> logging.apache.org ReportedBy: keiichi.fujito <at> hp.com Unfortunately, our system which uses log4j 1.2.15. encountered the same bug that was reported in Bug#: 38137 Comment #16. This bug seems not to be discussed for the final fix for several months… Is this bug going to fix in near future? Here is the thread dump: Found one Java-level deadlock: ============================= "Thread-1": waiting to lock monitor 6000000000587e40 (object 9fffffffcb409a68, a java.util.ArrayList), which is held by "pool-1-thread-41460" "pool-1-thread-41460": waiting to lock monitor 6000000000588230 (object 9fffffffcb4d9b28, a org.apache.log4j.spi.RootLogger),(Continue reading)
RSS Feed