Hi Chris,
On 12/06/18 8:05 PM, Chris Hegarty wrote:
I filed the following JIRA to track this issue: https://bugs.openjdk.java.net/browse/JDK-8204864 I think that the most appropriate course of action is to consistently throw the IOException subtype, ConnectionException ( with the original cause ), for any failures encountered during a connect operation. Rather than trying to deal with the low-level NIO exceptions.
Makes sense.
I’ll resolve this issue in the sandbox, and it will likely make the next refresh [1], along with all other comments and feedback that we’ve received to date.
Thank you. -Jaikiran
