Catching Exceptions Caused by Temporary Network Errors

Question

I need to download some URLs, and it may happen that some kind of exception may occur during operations, for example java.net.NoRouteToHostException. I consider this a temporary exception, as the download may be successful if you try again after a while.
Therefore, I would like to catch all those exceptions related to timing errors, and I started with them: java.net.NoRouteToHostException, java.net.SocketException
Can you list any other exceptions, such as these?

Answer 1

java.net.SocketExceptionis a parent java.net.NoRouteToHostException, so you can only catch a parent. The remaining children are SocketExceptionequal BindException, ConnectExceptionand PortUnreachableException. Maybe it’s okay to catch only SocketExceptionin your case ...

Answer 2

One pattern that is sometimes useful for solving temporary errors in repeated actions is to define the error callback interface and some classes that implement it; when an error occurs, let the callback know and let it decide whether to throw an exception or whether the action should be repeated. Since existing communication classes do not match this pattern, it may be necessary to catch their exceptions and turn them into callbacks.

, , . , , , .., , - "".

Answer 3

@reef java.net.NoRouteToHostException exntends java.net.SocketException, java.net.SocketException, . java.net.SocketException IOException, , , . IO .

Answer 4

HttpRetryException - . , java.net, SocketException?

( )

try {
....
} catch(Exception e) {
    if(e.getClass().getPackage().getName().equalsIgnoreCase("java.net")) {
        retry();
    }
}