On Fri, 2005-11-04 at 09:19 -0800, Mark Womack wrote:
>
>
> I would much rather get on with 1.3 and do it the right way there.
I'd rather we think of something better for 1.3 than waste time spinning
on this problem for 1.2.
You may be able to change every class in log4j to have more fine gra
Well, I was thinking about something we could do quickly for 1.2
without messing around with the existing code at all. All the
stuff I talked about would be in the wrapper class itself and would not
require any changes in the configurator or appender classes.
Maybe changes are required in other p
On Thu, 3 Nov 2005, Mark Womack wrote:
| The wrapper class would only be in 1.2 and really only used to avoid making
| everyone take the "big" change in the new version of 1.2. I am assuming that
| we will do the right thing in 1.3 to not require the use of the wrapper
| class.
|
| The wrapper cl
On 04/11/2005, at 1:38 PM, Mark Womack wrote:
The wrapper class would only be in 1.2 and really only used to
avoid making everyone take the "big" change in the new version of
1.2. I am assuming that we will do the right thing in 1.3 to not
require the use of the wrapper class.
So, tha
The wrapper class would only be in 1.2 and really only used to avoid
making everyone take the "big" change in the new version of 1.2.
I am assuming that we will do the right thing in 1.3 to not require the
use of the wrapper class.
The wrapper class would need to have a special (and potentially c
that's very intriguing on face value. Bit of maintenance effort? If this is for 1.2, are you saying that a 1.3 upgrade by our users would be required to 'drop' their use of the wrapper classes in favour of something else, or do you see these wrapper impl's staying supported features longer term?I
OK, stop me if this sounds completely crazy. It might.
What if we created a wrapper class for subclasses of AppenderSkeleton
that implemented Elias's version of doAppend with the changed
synchronization logic? That wrapper class would be part of the
1.2 release but would not be used in the curre
Yes, it is on the "list" for 1.3.
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.
-MarkOn 10/31/05
Hello Elias,
>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 mor
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
10 matches
Mail list logo
