2014/5/26 20:01 -0700, michael.x.mcma...@oracle.com: > I think it should be throwing a SocketException rather than a > NotYetBoundException to be consistent with ServerSocket.accept()
No, NotYetBoundException is the correct exception here. The NIO exception hierarchy was intentionally designed to be richer than just "SocketException". Consistency with the exceptions thrown by the original java.net APIs is an anti-goal. - Mark
