DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=43568>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=43568 Summary: Deadlock in Log4j when logging inside exception stack trace Product: Log4j Version: 1.2 Platform: Sun OS/Version: Solaris Status: NEW Severity: major Priority: P1 Component: Other AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] - Log4j is configured with a RootLogger and a specific Logger for the package com.siemens, both configured to use the same RollingFileAppender. - Thread 1: a class in the package X logs an exception outside the package X - Thread 2: a class outside the package X tries to log another message ull description of deadlock: [T1]: Thread 1 acquires a lock on the specific Logger of package X [T1]: As a consequence Thread 1 acquires a lock on the RollingFileAppender [T2]: Thread 2 wants to log something and as such acquires a lock on RootLogger. [T2]: To perform the logging, Thread 2 waits to get a lock on the RollingFileAppender [T1]: The logging of the exception in Thread 1 also wants to write stuff to the log and as it is outside the X package wants a lock on the RootLogger which is owned by Thread 2 already. The problem occured with Apache Axis 1.4 which appearantly shows this behaviour of logging during the generation of exception stack traces. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
