Why does `TimeoutHandler` get to throw `Exception`?

[Palmr]

TimeoutHandler::onTimeout throws a checked exception if the implementation is unable to handle the timeout.

BatchEventProcessor::notifyTimeout catches Throwable, so no need for checked exception type.

The exception gets passed to the exception handler which may handle or bail out of the BatchEventProcessor::processEvents depending on the ExceptionHandler implementation.

This is leaning towards use of exceptions for control flow and perhaps we could look at returning something useful from TimeoutHandler::onTimeout instead?

[SteafanMrZhou]

I think the ExceptionHandler is only leaning towards to graph all type exceptions and distributing to exception handler by excetion type.
Liking this way,TimeoutHandler::onTimeout can deal with itself exception and return something useful information about timeout:waitTime,isInterrupted,isDeadLock,etc.
Anykinds exception will deal with like this in disruptor.

[grumpyjames]

There's a further point raised from #429 which makes me think "isn't the whole of timeout handling massively exception-as-control-flow ?"