java.net.SocketException

Connection reset java.net.SocketException: Connection reset


Samebug tips2

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.

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

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.


Solutions on the web6576

Solution icon of apache
via hc-httpclient-users by Oleg Kalnichevski, 1 year ago
Connection reset>java.net.SocketException: Connection reset

Solution icon of apache
via hc-httpclient-users by Boxer, Aaron, 1 year ago
Connection reset>java.net.SocketException: Connection reset

Solution icon of apache
via hc-httpclient-users by Oleg Kalnichevski, 1 year ago
Connection reset>java.net.SocketException: Connection reset

Solution icon of github
Connection reset: java.net.SocketException: Connection reset

Solution icon of oraclecommunity
via Oracle Community by 843790, 1 year ago
Connection reset java.net.SocketException: Connection reset

Solution icon of web
via oracle.com by Unknown author, 10 months ago
Connection reset java.net.SocketException: Connection reset

Solution icon of web
via co.jp by Unknown author, 7 months ago
Connection reset java.net.SocketException: Connection reset

Solution icon of web
via oracle.com by Unknown author, 7 months ago
Connection reset java.net.SocketException: Connection reset

Solution icon of apache
via hc-httpclient-users by Boxer, Aaron, 1 year ago
Connection reset>java.net.SocketException: Connection reset

Solution icon of apache
via hc-httpclient-users by Boxer, Aaron, 1 year ago
Connection reset>java.net.SocketException: Connection reset

Stack trace

  • java.net.SocketException: Connection reset java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at weblogic.socket.PosixSocketMuxer.readBytesProblem(PosixSocketMuxer.java:876) at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:767) at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:694) at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 11 months ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
393 more bugmates