You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4net-dev@logging.apache.org by "Ron Grabowski (Closed) (JIRA)" <ji...@apache.org> on 2012/04/11 02:39:21 UTC

[jira] [Closed] (LOG4NET-332) 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

     [ https://issues.apache.org/jira/browse/LOG4NET-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Grabowski closed LOG4NET-332.
---------------------------------

    Resolution: Duplicate

See LOG4NET-1
                
> 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