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

Martin Schröder updated LOG4J2-1163:
------------------------------------
    Description: 
We are using the attached configuration with log4j2, which tries to use a 
failover appender. But on startup we get the message
{{ERROR appender Failover has no parameter that matches element Failovers}}

On stackoverlow there is this discussion: 
[http://stackoverflow.com/a/31194308/821436]

Is this a bug in the way failover appenders are handled or is there and error 
in the configuration?

  was:
We are using the attached configuration with log4j2, which tries to use a 
failover appender. But on startup we get the message
ERROR appender Failover has no parameter that matches element Failovers

On stackoverlow there is this discussion: 
http://stackoverflow.com/a/31194308/821436

Is this a bug in the way failover appenders are handled or is there and error 
in the configuration?


> ERROR appender Failover has no parameter that matches element Failovers
> -----------------------------------------------------------------------
>
>                 Key: LOG4J2-1163
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1163
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 2.4.1
>            Reporter: Martin Schröder
>         Attachments: log4j2.xml
>
>
> We are using the attached configuration with log4j2, which tries to use a 
> failover appender. But on startup we get the message
> {{ERROR appender Failover has no parameter that matches element Failovers}}
> On stackoverlow there is this discussion: 
> [http://stackoverflow.com/a/31194308/821436]
> Is this a bug in the way failover appenders are handled or is there and error 
> in the configuration?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to