FileChannel implements InterruptibleChannel, help or hindrance?

Alan Bateman Alan.Bateman at
Wed Feb 28 19:58:28 UTC 2018

On 28/02/2018 19:22, Brian Burkhalter wrote:
> Providing dynamic toggling of interruptibility would introduce 
> complexity that we probably don’t want. The OpenOption approach is 
> appealing but the InterruptibleChannel specification does not appear 
> to admit much flexibility on this point:
> [Interrupting a thread] blocked in an I/O operation on an 
> interruptible channel […] will cause the channel to be closed, the 
> blocked thread to receive a |ClosedByInterruptException| 
> <>, 
> and the blocked thread's interrupt status to be set.
Yes, it would mean clarifications to allow that, maybe even an 
isInterruptible method on this interface to allow for testing.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the nio-dev mailing list