logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <ralph.go...@dslextreme.com>
Subject Re: LOG4J2-291 and error handling
Date Tue, 16 Jul 2013 16:39:37 GMT
As a general rule exceptions in appenders that cause the log event to fail to be written should
be percolated.  AppenderControl has the ability to suppress them if that is what the user
wants.  But the FailoverAppender can't do its work unless the exceptions percolate to it.

Ralph

On Jul 16, 2013, at 8:52 AM, Nicholas Williams wrote:

> If it helps, check out LOG4J2-291. I may be handling errors
> incorrectly in the JDBC/JPA/NoSQL appenders. If an exception is thrown
> within the *Manager write methods, should I just let that exception
> propagate (wrapping it if it's a checked exception that I can't
> throw)? Should I wrap all exceptions in some standard exception
> (LoggingException or something similar)? Right now I'm catching
> exceptions and logging them using the SimpleLogger. I may need to
> change that behavior.
> 
> Nick
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> 


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


Mime
View raw message