You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2003/12/12 20:49:25 UTC

DO NOT REPLY [Bug 24159] - Log4J can create deadlock conditions

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

eross@m-qube.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Other                       |Appender



------- Additional Comments From eross@m-qube.com  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: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org