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.

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.


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:


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

  • Demo doesn't start in Linux 64-bit
    via djproject by rdenaux
  • Can't run the SWTDemo jar
    via djproject by lucasp1
  • java.lang.UnsatisfiedLinkError
    via djproject by kapamarou
  • SyntaxHighlighting doesn't work
    via djproject by raviaa
  • JBoss Community / Mailing Lists
    via by Unknown author,
    • java.lang.RuntimeException: Connection reset at at at<init>( at$SwingOutProcessSocketsMessagingInterface.<init>( at$OutProcess.createOutProcessMessagingInterface( at$OutProcess.createOutProcessCommunicationChannel( at at at Caused by: Connection reset at at at at at$ at$PeekInputStream.readFully( at$BlockDataInputStream.readShort( at at<init>( at ... 8 more

    Users with the same issue

    Unknown visitor1 times, last one,
    40 times, last one,
    2 times, last one,
    Unknown visitor1 times, last one,
    1 times, last one,
    189 more bugmates