https://issues.apache.org/bugzilla/show_bug.cgi?id=44888
--- Comment #6 from Ralph Goers <[EMAIL PROTECTED]> 2008-05-16 00:49:47 PST ---
I ran the build and it was successful. I modified the Appender code I showed
below to print the stacktrace and the info in LocationInfo before it was
correc
I grabbed the 1.2.15 sources, built them, and then tried to run the
regression tests -- in preparation for making changes and then verifying
no tests fail.
Unfortunately, I get the following failure:
Minimum:
[junit] Running org.apache.log4j.MinimumTestCase
[junit] Testsuite:
We as many others have been bitten by the synchronization nuances of log4j.
Attached is a proposed patch to reduce the scope of the problem. No,
this is not yet regression tested due to the issues I e-mailed about
previously with the regression test suite, but I'd like to spur some
discussion
I made a slight adjustment to the pre-Java-5 solution and replaced it
(unconditionally here, though this could easily be made conditional)
with a Java 5 implementation.
Jess Holle wrote:
We as many others have been bitten by the synchronization nuances of
log4j.
Attached is a proposed patch
By the way, I am aware that these changes don't (yet) address the
opportunity for deadlock. That'll come later (hopefully).
This just *reduces* both the bottleneck and deadlock potential.
Jess Holle wrote:
I made a slight adjustment to the pre-Java-5 solution and replaced it
(unconditionally
In case it's not obvious the other major issue I'm alluding to is the
synchronization in AppenderSkeleton.
This is harder to remove without breaking things -- and might be better
addressed by an AppenderSkeleton2 or by an extra argument to the
AppenderSkeleton constructor indicating the desire
