java.net.SocketException

If you like a tip written by other Samebug users, mark is as helpful! Marks help our algorithm provide you better solutions and also help other users.
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.

  • Connection Failure & SSL Certificate
    via by Louis,
  • Exception when request http document?
    via by 3004,
  • <HTTP> Connection failure
    via by 3004,
  • Login timeout
    via by 3004,
  • <E><HTTP>Connection failure
    via by Mark Hayes,
  • java.net.SocketException
    via by 3004,
  • What make suck Exception?
    via by 3004,
  • &lt;E&gt;&lt;HTTP&gt;Connection failure
    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,
    • 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)

    Users with the same issue

    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    tvrmsmith
    1 times, last one,
    musketyr
    15 times, last one,
    gamebusterz
    2 times, last one,
    209 more bugmates