Skip to content

Handle EHOSTUNREACH errors in io.netty.channel.unix.Errors (#13317)#13318

Merged
normanmaurer merged 1 commit intonetty:4.1from
tristantarrant:EHOSTUNREACH
Apr 3, 2023
Merged

Handle EHOSTUNREACH errors in io.netty.channel.unix.Errors (#13317)#13318
normanmaurer merged 1 commit intonetty:4.1from
tristantarrant:EHOSTUNREACH

Conversation

@tristantarrant
Copy link
Copy Markdown
Contributor

Fixes #13317

    Motivation:

    We should throw a NoRouteToHostException when a socket connection fails with EHOSTUNREACH in the same way as
    ENETUNREACH.

    Modifications:

    Add handling for EHOSTUNREACH

    Result:

    Correct exception is thrown.
@franz1981
Copy link
Copy Markdown
Contributor

Good catch @tristantarrant did you already signed our license agreement?
Last point of https://netty.io/wiki/developer-guide.html#checklist

@tristantarrant
Copy link
Copy Markdown
Contributor Author

Yep, I have signed the CLA

@normanmaurer normanmaurer merged commit 76d83fe into netty:4.1 Apr 3, 2023
@normanmaurer normanmaurer added this to the 4.1.91.Final milestone Apr 3, 2023
normanmaurer pushed a commit that referenced this pull request Apr 3, 2023
…13318)

Motivation:

    We should throw a NoRouteToHostException when a socket connection fails with EHOSTUNREACH in the same way as
    ENETUNREACH.

    Modifications:

    Add handling for EHOSTUNREACH

    Result:

    Correct exception is thrown.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

io.netty.channel.unix.Errors should rethrow EHOSTUNREACH as NoRouteToHostException instead of generic ConnectException

3 participants