https://issues.apache.org/jira/browse/LOG4J2-1453
On Thu, Jun 30, 2016 at 5:56 PM, Remko Popma wrote:
> At the time it was on purpose but now I think about it more I agree it is
> better to use some timeout.
> Not sure when I will be able to get to it. Would you mind raising a Jira
> for this so
Yes no problem. I can also provide a PR for it if you want.
On Thu, Jun 30, 2016 at 5:56 PM, Remko Popma wrote:
> At the time it was on purpose but now I think about it more I agree it is
> better to use some timeout.
> Not sure when I will be able to get to it. Would you mind raising a Jira
> f
AsyncAppender has a shutdownTimeout parameter. It would be good to have
something similar for async loggers. It is important to not block JVM
shutdown forever.
On Thu, Jun 30, 2016 at 5:56 PM, Remko Popma wrote:
> At the time it was on purpose but now I think about it more I agree it is
> better
At the time it was on purpose but now I think about it more I agree it is
better to use some timeout.
Not sure when I will be able to get to it. Would you mind raising a Jira
for this so we won't forget about it?
Remko
On Thu, Jun 30, 2016 at 4:10 AM, David Leonhartsberger
wrote:
> I was just l
I was just looking at the AsyncLoggerDistruptor#stop() and figured out that
the shutdown time is not configurable and it even could be blocking forever
waiting that the Disruptor backlog has been processed.
// Calling Disruptor.shutdown() will wait until all enqueued events are
fully processed,
/
