Bug 470727 - Thread Starvation of selector wakeups.
Added comment on running non-blocking code immediately.
This commit is contained in:
parent
4e3b400550
commit
f62305b5a5
|
@ -100,20 +100,23 @@ public class SelectChannelEndPoint extends ChannelEndPoint implements ManagedSel
|
|||
if (LOG.isDebugEnabled())
|
||||
LOG.debug("onSelected {}->{} for {}", oldInterestOps, newInterestOps, this);
|
||||
|
||||
|
||||
boolean readable = (readyOps & SelectionKey.OP_READ) != 0;
|
||||
boolean writable = (readyOps & SelectionKey.OP_WRITE) != 0;
|
||||
|
||||
// Call non blocking directly
|
||||
// Run non-blocking code immediately.
|
||||
// This producer knows that this non-blocking code is special
|
||||
// and that it must be run in this thread and not fed to the
|
||||
// ExecutionStrategy, which could not have any thread to run these
|
||||
// tasks (or it may starve forever just after having run them).
|
||||
if (readable && getFillInterest().isCallbackNonBlocking())
|
||||
{
|
||||
getFillInterest().fillable();
|
||||
readable=false;
|
||||
_runFillable.run();
|
||||
readable = false;
|
||||
}
|
||||
if (writable && getWriteFlusher().isCallbackNonBlocking())
|
||||
{
|
||||
getWriteFlusher().completeWrite();
|
||||
writable=false;
|
||||
_runCompleteWrite.run();
|
||||
writable = false;
|
||||
}
|
||||
|
||||
// return task to complete the job
|
||||
|
|
Loading…
Reference in New Issue