logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giovanni De Martino <giovanni.de.mart...@gmail.com>
Subject R: Log4j 2.x AsyncLogger
Date Thu, 19 Mar 2015 00:53:24 GMT
Many thanks Remko.
Just another question:
If the logger is connected to an Async Appender with the blocking parameter set to "false",
how is possible that the ringbuffer become full?


----- Messaggio originale -----
Da: "Remko Popma" <remko.popma@gmail.com>
Inviato: ‎19/‎03/‎2015 01:01
A: "Log4J Users List" <log4j-user@logging.apache.org>
Oggetto: Re: Log4j 2.x AsyncLogger

When the ringbuffer is full, calls to the logger become blocking calls. There is no mechanism
to discard log events. 

Best regards,
Remko

Sent from my iPhone

> On 2015/03/19, at 6:40, Giovanni De Martino <giovanni.de.martino@gmail.com> wrote:
> 
> Hi all,
> I'm currently using Log4j 2.1 in a production environment.
> I'm using all Async Logger with a RingBuffer of around 130.000 entries and
> then an AsyncAppender towards MongoDB.
> I'd like to kindle ask you following question:
> what happen is the RingBuffer of the AsynLogger (not the Async Appender)
> become full?
> It is a blocking buffer or old log entries not even passed to the appender
> are discarded and new ones overwrite then into the ring?
> 
> Many thansk, giovanni
> 
> 
> -- 
> Giovanni De Martino
> giovanni.de.martino@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message