logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 41274] - Deadlock using log4j
Date Fri, 26 Jan 2007 04:12:42 GMT
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=41274>.
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=41274





------- Additional Comments From ravitx12@yahoo.com  2007-01-25 20:12 -------
This is definitely not a duplicate of 41214. This is a classic deadlock issue. 
I tried even with the latest version of log4j and noticed the same behavior.

The main problem is, we are calling log4j within the appender itself after 
log4j calls the appender. A fix for this got to be expensive as you need to 
lock all appenders for a logger when that logger is logging. Or you should 
atleast publish a guideline stating log4j should not be called from the 
appenders.

Thanks for looking into this.

Ravi

(In reply to comment #2)
> This looks remarkably similar to
> http://issues.apache.org/bugzilla/show_bug.cgi?id=41214.
> Which particular version of log4j are you running against? If the line 
numbers
> below correspond with the File object usage in 41214, then I think this can 
be
> resolved a dupe.



-- 
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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message