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.

  • Scheduler Problem
    via by Michael Vornkahl,
  • GitHub comment 8#29081162
    via GitHub by nicopal
  • Re: error during HTTPS recoding
    via by Philippe Mouawad,
    • Connection reset at at at at at

    Users with the same issue

    Unknown visitor1 times, last one,
    24 times, last one,
    1 times, last one,
    Unknown visitor1 times, last one,
    27 times, last one,
    263 more bugmates