We can't actually remove a published exchange from an active Disruptor.
Instead we prevent processing of the exchange by setting a Property on the exchange and the value
would be an AtomicBoolean. This is set by the Producer and the Consumer would look up that Property and
check the AtomicBoolean. If the AtomicBoolean says that we are good to proceed, it will process the
exchange. If false, it will simply disregard the exchange.
But since the Property map is a Concurrent one, maybe we don't need the AtomicBoolean. Check with Simon.
Also check the TimeoutHandler of the new Disruptor 3.0.0, consider making the switch to the latest version.