logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <lis...@qos.ch>
Subject Re: ErrorHandler in log4j 1.3
Date Tue, 14 Mar 2006 20:01:54 GMT

The ErrorHandler idea sounds good but in practice it leads to a false sense 
of security, even worse, under certain circumstances its indiscriminate use 
can result in application failure. I think it is better to leave the 
implementation of the fallback mechanism to the failing appender instead of 
a general approach which does yield good results under fire.

At 05:41 PM 3/14/2006, Jonathan Beer wrote:
>I'm using log4j1.3-alpha8.
>I see that in alpha8 the ErrorHandler interface has been deprecated.
>What is the fallback method that will be used in 1.3 when the appender is
>not available (for example, with a DBAppender, if the connection is refused,
>or with a FileAppender without the proper permissions)?
>I thought the ErrorHandler mechanism was fairly useful with just a few
>drawbacks.  I was using the FallbackErrorHandler
>   - I didn't ever figure out how to have the FallbackErrorHandler check for
>the original appender to be available again after a certain period
>   - The first message was completely dropped when log4j switched appenders
>to the FallbackErrorHandler appender
>If anybody has any information about fallback appenders in log4j 1.3, or are
>using 1.3 with a homegrown work around, please advise.

Ceki Gülcü

To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org

View raw message