[
https://issues.apache.org/jira/browse/LOG4NET-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251210#comment-13251210
]
Ron Grabowski commented on LOG4NET-332:
---------------------------------------
If the AdoNetAppender fails and you switch over to a RollingFileAppender...when
do you switch back to the original appender? If/when you switch back to the
original appender do you try to re-send captured events? If you want to know if
an appender failed you could write a IErrorHandler that sends an email. You
could also write a ForwardingAppender that keeps track of a single active
appender and rolls to the next one if the first one fails.
> I'm looking for the ability to set up a hierarchy of appenders, if a log to
> an ADONETAppender fails, log4net could then log to one of more "back-up"
> appenders
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LOG4NET-332
> URL: https://issues.apache.org/jira/browse/LOG4NET-332
> Project: Log4net
> Issue Type: New Feature
> Components: Appenders
> Affects Versions: 1.2.9
> Environment: windows 7 , VS2010
> Reporter: stalinsubash
> Priority: Blocker
> Labels: patch
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Basically, I'm looking for the ability to set up a hierarchy of appenders so
> that if a log to an ADONETAppender fails, log4net could then log to one of
> more "back-up" appenders, for example, a RollingLogFile or SMTP
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
