8198562: (ch) Separate blocking and non-blocking code paths (part 1)

Alan Bateman Alan.Bateman at oracle.com
Wed Feb 28 19:34:34 UTC 2018

David Holmes pointed out off-list that the change to Thread.interrupt 
creates a potential issue when the nterrupt status is cleared just 
before a blocking I/O operations is start, e.g.

try { Thread.sleep(duration); } catch (InterruptedException e) { }

If something interrupts the sleep then it will race with the above as it 
clears the interrupt status and sets the blocker for the I/O operation. 
This may mean the blocking I/O operation completes with 
ClosedByInterruptedException and without the interrupt status being set.

To fix this then we need to go back to setting the interrupt status 
whilst holding the blockerLock. This means it works the same as JDK 
1.4-10 except that it handles the case where attempts its own interrupt 
status whilst in a blocking I/O (a source of potential deadlocks as we 
know from other discussions here).



More information about the nio-dev mailing list