java.net.SocketException

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.


rafael
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


rafael

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

  • Socket Exceptions in WebLogic 7SP2 with JDK 1.4.1
    via by Henry Grantham,
  • Error condition - Socket time out
    via by 3004,
  • WLS connection failure socket reset message
    via by Chengwei Lee,
  • SocketException and out.flush
    via by M. Parker,
  • What happens when peer goes away?
    via by janne,
    • 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) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)

    Users with the same issue

    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    263 more bugmates