There's something fishy here. So are there are non I/O events queued up that will not be serviced more quickly? Shouldn't adding events cause the Selector to wakeup so that it doesn't matter what the timeout value is.
- This doesn't quite work if we have a single thread doing everything. (which is why this bug is a non-issue when
the user has set a ThreadPool of size > 1 to be used by the server). - Kurchi
