Check for behavior changes related to the separation of blocking and non-blocking code paths for I/O channels

The following classes are flagged by this rule:

• java.nio.channels.SocketChannel
• java.nio.channels.ServerSocketChannel
• java.nio.channels.DatagramChannel
• java.nio.channels.Pipe.SourceChannel
• java.nio.channels.Pipe.SinkChannel

Prior to Java 11, non-blocking and blocking I/O operations used the same codes path in the classes listed earlier. This implementation slowed I/O speed a reduced reliability. With this change there are multiple behavioral changes:

• The java.nio.channels.SocketChannel and java.nio.channels.ServerSocketChannel classes will now delay closing their underlying connections until the closing channel is flushed from it's registered selectors. If used in conjunction with netstat network monitoring you will notice a change in behavior that affect other libraries and applications selection operations.
• I/O operations invoked on a selectable channel configured non-blocking and with interrupt status does not close the channel.
• When invoking configureBlocking(false) on a selectable channel it will block until all blocking I/O operations are finished.

For more information, see:

• The java.nio.channels.SocketChannel Javadoc.
• The java.nio.channels.ServerSocketChannel Javadoc.
• The java.nio.channels.DatagramChannel Javadoc.
• The java.nio.channels.Pipe.SourceChannel Javadoc.
• The java.nio.channels.Pipe.SinkChannel Javadoc.

For more information on the behavior change in Java 11, see the Removed APIs in JDK 11 page.