[
https://issues.apache.org/jira/browse/LOG4J2-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358955#comment-14358955
]
Ralph Goers commented on LOG4J2-975:
------------------------------------
Can you provide the output from setting status="debug" on the configuration
element along with the full log4j configuration file?
> Failover Appender does not start if primary appender fails
> ----------------------------------------------------------
>
> Key: LOG4J2-975
> URL: https://issues.apache.org/jira/browse/LOG4J2-975
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.2
> Environment: Windows-7
> Reporter: Ronald C Albury
>
> We are supposed to log to a network share - but sometimes it is not
> available. I created a Failover appender with a RollingFile appender to the
> network share as the primary, and a RollingFile appender to a local drive as
> a failover. If the network share is not available when my application starts,
> the Failover appender fails in its entirety and nothing is logged anywhere.
> <Failover name="MyFile" primary="ShareFile">
> <Failovers>
> <AppenderRef ref="LocalFile" />
> <AppenderRef ref="MyConsole" />
> </Failovers>
> </Failover>
> 2015-03-12 12:06:49,717 ERROR Attempted to append to non-started appender
> MyFile
> 2015-03-12 12:06:49,717 ERROR FailoverAppender MyFile did not start
> successfully
> 2015-03-12 12:06:49,717 ERROR Attempted to append to non-started appender
> MyFile
> 2015-03-12 12:06:49,717 ERROR FailoverAppender MyFile did not start
> successfully
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
