You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Constantin Ungureanu (JIRA)" <ji...@apache.org> on 2016/02/10 19:59:18 UTC
[jira] [Created] (LOG4J2-1267) AsyncLogger.stop() method is needed
Constantin Ungureanu created LOG4J2-1267:
--------------------------------------------
Summary: AsyncLogger.stop() method is needed
Key: LOG4J2-1267
URL: https://issues.apache.org/jira/browse/LOG4J2-1267
Project: Log4j 2
Issue Type: Bug
Components: API
Affects Versions: 2.5
Reporter: Constantin Ungureanu
The AsyncLogger.stop() method was used to prevent the exception bellow. Now with the 2.5 version, this was removed. Is there a workaround to fix this?
Feb 10, 2016 8:43:59 PM com.lmax.disruptor.FatalExceptionHandler handleEventException
SEVERE: Exception processing: 557627 org.apache.logging.log4j.core.async.RingBufferLogEvent@45c7b5da
java.lang.InterruptedException
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(Unknown Source)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(Unknown Source)
at com.lmax.disruptor.BlockingWaitStrategy.waitFor(BlockingWaitStrategy.java:45)
at com.lmax.disruptor.ProcessingSequenceBarrier.waitFor(ProcessingSequenceBarrier.java:56)
at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:124)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org