Consider adding a Java SE Exception type, maybe java.net.ConnectionReset, that is thrown when a socket is reset, rather than a SocketException with its detail message containing a String similar to "Connection reset by peer" ( may differ per platform ). This will help with error handling of this common situation.

The following discussion in the mail archives provide additional information and background:

http://mail.openjdk.java.net/pipermail/net-dev/2016-August/010178.html
http://mail.openjdk.java.net/pipermail/net-dev/2016-September/010257.html
http://mail.openjdk.java.net/pipermail/net-dev/2016-October/010356.html