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.

  • SocketException WLS 6.1 JMS
    via by Rakesh Aggarwal,
  • POSIX ProcessSockets error message
    via by John Wickstrom,
  • User permission problem
    via by Arumugam Appadurai,
  • Strange exception
    via by sdaf...@sffrewrf.org,
  • java.net.SocketException: No such file or directory
    via by Jacek Laskowski,
    • java.net.SocketException: Connection shutdown: JVM_recv in socket input stream read at java.net.SocketInputStream.socketRead(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:90)

    Users with the same issue

    ivanszkypeter
    40 times, last one,
    linxiaolong
    2 times, last one,
    Unknown visitor1 times, last one,
    tvrmsmith
    1 times, last one,
    Михайло Тітов
    1 times, last one,
    209 more bugmates