I guess I am not understanding what you want.
Here's what is in my log:
2016-02-16 16:31:36,337 main DEBUG Building Plugin[name=failovers,
class=org.apache.logging.log4j.core.appender.FailoversPlugin].
2016-02-16 16:31:36,337 main DEBUG createFailovers(={STDERR})
2016-02-16 16:31:36,337 main DEB
What about the rest please?
Gary
On Thu, Feb 18, 2016 at 12:30 PM, Tara Czutno
wrote:
> I did provide the exact error message:
> "ERROR appender Failover has no parameter that matches element Failovers"
>
> On Thu, Feb 18, 2016 at 10:32 AM, Apostolis Giannakidis <
> ap.giannaki...@gmail.com> wr
I did provide the exact error message:
"ERROR appender Failover has no parameter that matches element Failovers"
On Thu, Feb 18, 2016 at 10:32 AM, Apostolis Giannakidis <
ap.giannaki...@gmail.com> wrote:
> Tara,
>
> I think that it would be useful to provide us with the exact error message
> that
Tara,
I think that it would be useful to provide us with the exact error message
that you see, your exact configuration and versions as well as the exact
steps that one must perform to reproduce the same behavior.
On Thu, Feb 18, 2016 at 5:28 PM, Tara Czutno
wrote:
> I am trying to use Failover
I am trying to use Failover Appender but got an error message.
ERROR appender Failover has no parameter that matches element Failovers
I saw this bug https://issues.apache.org/jira/browse/LOG4J2-878.
Is FailoverAppender working but just printing out an incorrect error message
- OR -
Is FailoverA
We have noticed this behavior on app servers running either JBOSS EAP 6.4 or
Wildfly 9.0.1 Final.
We are using the Console appender within our log4j2.xml file for our web-app
and we are seeing that any log4j2 messages written to the log are formatted as
double-spaced. Removing the "%n" from o
