JEP-353 - Socket.connect now throws NoRouteToHostException as against ConnectException previously

Jaikiran Pai jai.forums2013 at gmail.com
Tue Aug 24 03:09:35 UTC 2021


>
>> Do you connections to the Apache HTTP client library and the retry 
>> code that is looking for specific exceptions? From a distance it 
>> seems very fragile and depending on very implementation specific 
>> behavior. I wonder if it has ever been tested on Windows or with an 
>> untimed connect.
>
> I am not involved in the Apache HTTP client library project. However, 
> I will go ahead and open a discussion in their mailing list and bring 
> this issue to their attention, so that they can decide how to deal 
> with it.
>
> Thank you for your help and the explanation.

This has now been fixed in the Apache HTTP client library to no longer 
treat these two exception types differently when it comes to retry 
handling logic https://github.com/apache/httpcomponents-client/pull/311

-Jaikiran



More information about the net-dev mailing list