DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24159>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24159 Log4J can create deadlock conditions [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2003-12-18 20:20 ------- Elias, This bug is impossible to fix as long as log4j holds any exclusive lock while rendering the message object. The way log4j is designed, the rendering of the message object is done at the latest possible moment, that is when formatting the log message. If log4j holds to any lock at that moment (when rendering the object) a deadlock will occur. In log4j 1.2.8, the lock is on a logger object. In log4j version 1.3, the lock is on the appender itself even if locks on loggers are non-exclusive read-write locks. In short, either we modify our code making log4j thread *unsafe* or you change your code. The former is not an option. As such, I am marking this report as WONTFIX. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
