logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Remko Popma <remko.po...@gmail.com>
Subject Re: What's the AsyncLoggerConfig thread?
Date Fri, 22 Aug 2014 18:22:23 GMT
This is the background thread that takes log events out of the disruptor ringbuffer and passes
them to their appender(s). So this is where the actual logging (to disk for example) takes
place. This is a daemon thread so it should not keep your app alive longer than necessary.

A call to asynccontext.stop() will ensure the ringbuffer contents are fully processed before

Sent from my iPhone

> On 2014/08/22, at 19:56, Mariano Gonzalez <mariano.l.gonzalez@gmail.com> wrote:
> Hello,
> Could you explain what's the purpose of this thread? It seems to keep on
> running when my application is undeployed.
> I looked at the code and it seems to be a thread responsible for
> dispatching events to Disruptor, but if that's the case then the name may
> not be very descriptive IMHO. Can you confirm what's the purpose of this
> thread and that it should stop after the logging context receives the
> stop() message?
> Thanks!

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

View raw message