Async Appender uses a different mechanism than Async Loggers (and a different queue, separate from the AsyncLogger ringbuffer).
With AsyncAppender it is possible to control the blocking behaviour with a config parameter. In contrast, Async Loggers always block if the ringbuffer is full. Best regards, Remko Sent from my iPhone > On 2015/03/19, at 9:53, Giovanni De Martino <[email protected]> > wrote: > > 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" <[email protected]> > Inviato: 19/03/2015 01:01 > A: "Log4J Users List" <[email protected]> > 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 <[email protected]> >> 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 >> [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]
