Can not access Disruptor internals when starting the project about exchange-core HOT 4 CLOSED

Hi @lannuo yes this is a known bug in the last commit.
Will be resolved very soon.
Disruptor uses older blocking mechanism in the last release, not "mutex"- I forgot about that so now exchange core fails.

from exchange-core.

final Field f = getField(BlockingWaitStrategy.class, "mutex");

Hi Maksim, how do you think replace "mutex" to "processorNotifyCondition" ?

from exchange-core.

and replace
synchronized (mutex) {
sequenceBarrier.checkAlert();
mutex.wait();
}
with
sequenceBarrier.checkAlert();
mutex.wait();

from exchange-core.

This issue is fixed for mine, many thanks.

from exchange-core.