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 Google Groups by Louis, 2 years ago
via Google Groups by gopal, 11 months ago
Socket closed
via Oracle Community by 3004, 1 year ago
Socket closed
via Oracle Community by 3004, 1 year ago
via Google Groups by Per Lovdinger, 11 months ago
A connection with a remote socket was reset by that socket.: A connection with a remote socket was reset by that socket.
via Google Groups by sad, 2 years ago
A connection with a remote socket was reset by that socket.: A connection with a remote socket was reset by that socket.
java.net.SocketException: Socket closed at java.net.SocketInputStream.socketRead(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:86) at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:209) at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)