Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    Expert tip

    It's possible you're trying to write to a connection that's already closed. Another cause for this is that you closed the socket with unread data in the socket receive buffer.

  2. ,
    Expert tip

    This might be caused by unmatching versions of SSL. Java starts normally with SSLv2 and your server might not be able to negotiate. You have to force Java to use SSLv3. See this comment: https://goo.gl/hx0YB3

Solutions on the web

via Oracle Community by David Knierim, 1 year ago
Connection reset 13:12:18.567 13:12:27.531 13:12:18.567
via Google Groups by Mike Riley, 2 years ago
via Oracle Community by 843790, 1 year ago
Connection reset
via Oracle Community by 843790, 1 year ago
Connection reset
via Oracle Community by 843859, 1 year ago
Connection reset
java.net.SocketException: Connection reset
13:12:18.567 13:12:27.531
13:12:18.567	at java.net.SocketInputStream.read(SocketInputStream.java:209)