Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Not A Problem
-
2.5
-
None
-
None
Description
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)