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.

  • the cluster for stateful session bean
    via by 3004,
  • java.net.SocketException: Connection timed out
    via by Unknown author,
  • SQL Exception for MS SQL
    via by shiv,
  • WL Server Crashes
    via by Gustavo Mejia,
  • <E><HTTP>Connection failure
    via by Mark Hayes,
  • Can't get jsp interpretation
    via by dsw...@attglobal.net,
  • Connection Failure & SSL Certificate
    via by Louis,
  • cannot parse POST parameters of request
    via by Unknown author,
  • Posix Performance Pack
    via by birdking,
  • cannot parse POST parameters of request
    via by Jeff Legendre,
    • java.net.SocketException: Connection reset by peer: JVM_recv in socket > input > > str > > eam read at java.net.SocketInputStream.socketRead(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:86)

    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