The last message in the thread is from 10/21. Do you have any update since then? I really hate leaving this hanging in 1.2. I would like to find a solution that does not break subclasses of AppenderSkeleton. Don't know what that would be yet.
-Mark
On 10/31/05, Elias Ross <[EMAIL PROTECTED]> wrote:
For your information: Log4j has the potential to create deadlocks at
the message rendering step. The JBoss team has been working on fixing
this issue.
http://jira.jboss.com/jira/browse/JBAS-2393
Scott Stark is trying two approaches. One is to fix the synchronization
code used in log4j 1.2.12 in JBoss through a patch, which may break user
appenders. The other is to create log4j-style appenders and DOM
configuration support for the JDK logging framework. You can read more
in the forum thread linked from the issue.
(This issue I opened about 2 years ago and hasn't really seen much
attention. http://issues.apache.org/bugzilla/show_bug.cgi?id=24159 )
I don't expect this to be fixed for 1.2, but I would hope it gets
addressed for 1.3 as part of the "must-fix list" for 1.3.
I'm not sure what sort of reasonable fix might be employed for the main
framework, I'm hoping to discuss that here.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
