I guess that AppenderLoggingException can be used for that purpose.
On Wed, Jan 13, 2016 at 10:53 PM, Ralph Goers
wrote:
> Your appender is automatically wrapped by an AppenderControl object. The
> AppenderControl will inspect the ignoreExceptions flag so your
I might be a good idea to allow Appenders to throw any exception. Having to
catch and wrap checked exceptions is annoying.
On Thu, Jan 14, 2016 at 6:50 AM, Ralph Goers
wrote:
> Why are you catching it at all? AppenderControl also takes care of
> handling logging the
I'm getting a little confused here. I also left out some information. We do
need to catch because for some of our appenders we log the errors to loggers
which will capture the errors in a central location.
If we didn't include any exception handling that would mean any type of
exception
Catch the exception, log it or whatever, then throw an AppenderLoggingException
chaining the original exception to it.
Ralph
> On Jan 14, 2016, at 7:08 PM, Nicholas Duane wrote:
>
> I'm getting a little confused here. I also left out some information. We do
> need to catch
You need to use a RuntimeException derivative. The whole point of not
swallowing Appender exceptions is that so something can be done based on
the exception. For instance, there's the FailoverAppender which lets you
switch to another Appender if the primary one starts to fail (e.g., network