Question: We want to empty the ringbuffer as fast as possible on shutdown, even if the handler threads are currently blocked #506
Description
Hello,
Currently we have the following problem.
We have a Incoming and a Outgoing Disruptor.
Sometimes the Disruptor Ringbuffer reaches the full capacity. Sometimes the Handlers on the Incoming Disruptor side have a blocking Thread, because some threads after the outgoing disruptor are not fast enough or some external system experiences problems.
We are using the RedHat JBoss EAP as a service and when we try to stop it these full Ringbuffers create issues because they are blocking threads, that cant be closed.
My Question was. Is there a way to force the ringbuffer to be emptied when we shutdown, so that all the blocked threads are released and the Beans can be destroyed.
Currently we are using LMAX Disruptor Version 3.3.4.
We are using the standard BlockingWaitStrategy.