On Mar 20, 2006, at 11:20 AM, Jonathan Beer wrote:
I'm currently using the DBAppender, and I'm looking through the API
and I
don't see anything that leads me to believe there's anything in
place for
handling errors with the appender. Is this true? If this is the
case, what
should I be doing to make this to happen?
I've searched the forums but found no useful information. This
leads me to
believe that either (a) people are not looking ahead to the 1.3
release and
using the 1.2.x ErrorHandler interface, (b) nothing ever fails and
therefore
there is no need for a backup appender, or (c) I have missed something
obvious. What are others doing to achieve the fallback in case of
appender
error?
Thanks,
Jonathan
The recent focus on 1.3 development has been to restore compatibility
with log4j 1.2 and save breaking changes for log4j 2.0. I believe
that log4j 1.2 style use of ErrorHandler has been broken in the log4j
1.3 code base, but I don't know that for sure and it isn't near to
top of the list of things to modify to restore log4j 1.2
compatibility. If you'd like to investigate how error reporting has
changed from log4j 1.2 and provide patches or suggestions to restore
log4j 1.2 behavior, it would be very helpful.
I do not anticipate that we would want to introduce any new error
reporting architecture in log4j 1.3. However, it would be good to
think about that in the log4j 2.0 development cycle.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
