We are currently using log4j2 version 2.0-RC1-SHAPSHOT.  The FlumeAppender is 
configured as an "Avro" appender (i.e. agent is configured only on the Flume 
side).  We have also been using Flume 1.4.  What we are seeing is not really a 
"failover" condition, however.  Admittedly, we are currently using only one 
Flume agent and need to configure at least 2 to address failover.  Still, if 
the Flume agents are down, this should not cause the application to hang, but 
it appears to be the case.
________________________________________
From: ralph.goers @dslextreme.com [[email protected]] On Behalf Of 
Ralph Goers [[email protected]]
Sent: Thursday, February 20, 2014 7:23 AM
To: Log4J Users List
Cc: [email protected]
Subject: Re: Log4j2 Logging to FlumeAppender when Flume agents are down

What version of Log4j are you using? Which variation of the Appender are you 
using? (Agent, embedded, persistent).

The latest log4j release upgraded the flume Appender to use Flume 1.4, with 
that version Flume is actually doing all the connectivity so any errors with 
regards to failover would be in Flume, not Log4j.

Sent from my iPad

> On Feb 19, 2014, at 2:46 PM, Michael Friedmann <[email protected]> 
> wrote:
>
> 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 
> addresses the underlying problem (i.e. this should not cause the application 
> to hang).  Is this a bug in log4j2 - I'll be happy to enter a ticket if that 
> is the case - or are there configuration settings that would resolve this 
> (that would be my preference).
>
> Any help is greatly appreciated.
>
> Thanks!
> Michael
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

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


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

Reply via email to