We are using a FlumeAppender under Log4j2. Currently, we have one Agent
configured. If the Flume agent is running, all is well. However, if the agent
goes down, this appears to cause the application to hang. We can configure
multiple Flume agents for failover, but I don't believe this addres
Hi,
My understanding is, that you just need this setting if and only if you use a
FailoverAppender. That way you can propagate an exception to other appenders,
if during the handling of a log message an exception occurs, say a JDBCAppender
can’t connect to a database.
So if I have a don’t use
Congrats, Nick!
On 19 February 2014 08:46, Ralph Goers wrote:
> Cogratulations, Nick!
>
> Sent from my iPhone
>
> > On Feb 19, 2014, at 4:12 AM, "Christian Grobmeier"
> wrote:
> >
> > Dear all,
> >
> > please welcome Nick Williams as the lastest member of the
> > Apache Logging PMC.
> >
> > Ni
Cogratulations, Nick!
Sent from my iPhone
> On Feb 19, 2014, at 4:12 AM, "Christian Grobmeier"
> wrote:
>
> Dear all,
>
> please welcome Nick Williams as the lastest member of the
> Apache Logging PMC.
>
> Nick made very valuable contributions esp to Log4j in the past
> and the current PMC
The Apache Log4j 2 team is proud to announce the Log4j 2.0-rc1 release!
Apache Log4j is a well known framework for logging application behavior. Log4j
2 is an upgrade to Log4j that provides significant improvements over its
predecessor, Log4j 1.x, and provides many of the improvements available
Dear all,
please welcome Nick Williams as the lastest member of the
Apache Logging PMC.
Nick made very valuable contributions esp to Log4j in the past
and the current PMC is very happy that he accepted our invitation.
Thanks Nick for your work so far and we are all looking forward
for more grea
