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=38137>. 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=38137 ------- Additional Comments From [EMAIL PROTECTED] 2006-07-03 14:53 ------- Curt, we have also experienced this exact problem in our production system. We are running a multi-clustered J2EE application. I would recommend increasing the priority on this Bug to P1 as this deadlock brings down our production system. We are implementing Boris' hotfix and will post the results as soon as they are available. If the hotfix is valid, I would also recommend a new release of log4j immediately to address the issue. We are currently using log4j 1.2.8. Thanks, Zev. -- 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]
