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.

  • clusterable stateful session beans
    via by 3004,
  • SocketException WLS 6.1 JMS
    via by Rakesh Aggarwal,
  • Socket Exceptions in WebLogic 7SP2 with JDK 1.4.1
    via by Henry Grantham,
  • WL Server Crashes
    via by Gustavo Mejia,
  • <E><HTTP>Connection failure
    via by Mark Hayes,
  • Socket error after every page
    via by sad,
  • POSIX ProcessSockets error message
    via by John Wickstrom,
  • Connection Failure & SSL Certificate
    via by Louis,
  • User permission problem
    via by Arumugam Appadurai,
    • java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read at java.net.SocketInputStream.socketRead(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:86) at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273) at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225) at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    Users with the same issue

    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    ivanszkypeter
    40 times, last one,
    linxiaolong
    2 times, last one,
    Unknown visitor1 times, last one,
    209 more bugmates