https://issues.apache.org/bugzilla/show_bug.cgi?id=41214
--- Comment #50 from msm <[email protected]> --- (In reply to comment #48) > Since you asked for thoughts.... Please test Log4j 2. Yes, the bug presented in this page is solved in log4j version 2. I tested using log4j-2.0-beta2 and no more deadlock happens. But, unfortunately (or, FORTUNATELY, it depends on the point of view), this version of log4j requires JDK/JRE 1.5 or later. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
