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 ---------------------------------------------------------------------------- Component|Other |Appender ------- Additional Comments From [EMAIL PROTECTED] 2003-12-12 19:49 ------- I'm wondering if this issue has been resolved in Log4j 1.3? I can lend my assistance, as I have dealt with multi-processor issues many times on our Solaris machines. It is also a performance problem, as you have to hold category locks while the appender is doing its thing. If you're appending to two disks, or to JMS and a Socket, then the IO throughput could be increased dramatically for multi-processor machines. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
