Hello Remko, I'm using 2.1. Any pointers ?
On Fri, Dec 19, 2014 at 11:20 AM, Remko Popma <remko.po...@gmail.com> wrote: > > We used to have this problem in older versions but these issues have been > addressed in 2.1 as far as I know. Which version are you using? > > Sent from my iPhone > > > On 2014/12/19, at 22:01, Mariano Gonzalez <mariano.l.gonza...@gmail.com> > wrote: > > > > Hello, > > > > I have an application in which I'm using all async loggers. When I stop > the > > LoggerContext, there're still some events waiting in disruptor's buffer > and > > when it tries to execute them the context is already closed and thus > those > > events are lost. > > > > Is there some kind of hook, callback or whatever I can use so that when > the > > context is stopped: > > > > > > - the loggers stop accepting new messages > > - the context waits for disruptor's buffer to be empty before actually > > stopping > > > > > > Thanks > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > >
