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.


rafaelrafael
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


rafaelrafael

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

  • Spawned from HERI-1292. Adapted from those comments: Certain kinds of failures-then-retries result in valid 'history' info from the previous attempt lingering in the CrawlURI -- causing us to issue a If-Modified-Since header, and get back a 304 (the file hasn't changed since the previous aborted-fetch). Example of the issue from one of the affected crawls: local-errors.log includes: 2007-10-09T18:36:33.378Z -3 412116 http://www.makezine.com/blog/archive/stop_motion7.gif EXXLRLRLRLRLRLRLREXL http://www.thenervousbreakdown.com/zoe_brock/ image/gif #04 2 20071009183632659+718 - http://www.myspace.com/symonds3 le:SocketException@HTTP java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at java.io.BufferedInputStream.read1(BufferedInputStream.java:256) at java.io.BufferedInputStream.read(BufferedInputStream.java:317) at org.archive.io.RecordingInputStream.read(RecordingInputStream.java:114) at org.archive.io.RecordingInputStream.readFullyOrUntil(RecordingInputStream.java:203) at org.archive.crawler.fetcher.FetchHTTP.innerProcess(FetchHTTP.java:523) at org.archive.crawler.framework.Processor.process(Processor.java:112) at org.archive.crawler.framework.ToeThread.processCrawlUri(ToeThread.java:302) at org.archive.crawler.framework.ToeThread.run(ToeThread.java:151) Note that the socket break occurred after headers read -- so 'history' headers could be saved. crawl.log includes minutes later: 2007-10-09T18:51:36.080Z 304 0 http://www.makezine.com/blog/archive/stop_motion7.gif EXXLRLRLRLRLRLRLREXL http://www.thenervousbreakdown.com/zoe_brock/ image/gif #02 2 20071009185136062+17 sha1:3I42H3S6NNFQ2MSVX7XZKYAYSCX5QBYJ http://www.myspace.com/symonds3 4t Note the unexpected 304 and '4t' (4 tries) annotation. This should be fixable by discarding history info on any unsuccessful fetch.
    via by Gordon Mohr,
  • Spawned from HERI-1292. Adapted from those comments: Certain kinds of failures-then-retries result in valid 'history' info from the previous attempt lingering in the CrawlURI -- causing us to issue a If-Modified-Since header, and get back a 304 (the file hasn't changed since the previous aborted-fetch). Example of the issue from one of the affected crawls: local-errors.log includes: 2007-10-09T18:36:33.378Z -3 412116 http://www.makezine.com/blog/archive/stop_motion7.gif EXXLRLRLRLRLRLRLREXL http://www.thenervousbreakdown.com/zoe_brock/ image/gif #04 2 20071009183632659+718 - http://www.myspace.com/symonds3 le:SocketException@HTTP java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at java.io.BufferedInputStream.read1(BufferedInputStream.java:256) at java.io.BufferedInputStream.read(BufferedInputStream.java:317) at org.archive.io.RecordingInputStream.read(RecordingInputStream.java:114) at org.archive.io.RecordingInputStream.readFullyOrUntil(RecordingInputStream.java:203) at org.archive.crawler.fetcher.FetchHTTP.innerProcess(FetchHTTP.java:523) at org.archive.crawler.framework.Processor.process(Processor.java:112) at org.archive.crawler.framework.ToeThread.processCrawlUri(ToeThread.java:302) at org.archive.crawler.framework.ToeThread.run(ToeThread.java:151) Note that the socket break occurred after headers read -- so 'history' headers could be saved. crawl.log includes minutes later: 2007-10-09T18:51:36.080Z 304 0 http://www.makezine.com/blog/archive/stop_motion7.gif EXXLRLRLRLRLRLRLREXL http://www.thenervousbreakdown.com/zoe_brock/ image/gif #02 2 20071009185136062+17 sha1:3I42H3S6NNFQ2MSVX7XZKYAYSCX5QBYJ http://www.myspace.com/symonds3 4t Note the unexpected 304 and '4t' (4 tries) annotation. This should be fixable by discarding history info on any unsuccessful fetch.
    via by Gordon Mohr,
  • Retry mongodb connection
    via GitHub by j0hnsmith
    ,
  • 404 error
    via GitHub by xuniyuqi
    ,
  • I/O-Error when connection is lost
    via GitHub by karfau
    ,
    • java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at java.io.BufferedInputStream.read1(BufferedInputStream.java:256) at java.io.BufferedInputStream.read(BufferedInputStream.java:317) at org.archive.io.RecordingInputStream.read(RecordingInputStream.java:114) at org.archive.io.RecordingInputStream.readFullyOrUntil(RecordingInputStream.java:203) at org.archive.crawler.fetcher.FetchHTTP.innerProcess(FetchHTTP.java:523) at org.archive.crawler.framework.Processor.process(Processor.java:112) at org.archive.crawler.framework.ToeThread.processCrawlUri(ToeThread.java:302) at org.archive.crawler.framework.ToeThread.run(ToeThread.java:151)

    Users with the same issue

    Nikolay RybakNikolay Rybak
    1 times, last one,
    mauritiusmauritius
    2 times, last one,
    Unknown visitor
    Unknown visitor1 times, last one,
    Unknown visitor
    Unknown visitor1 times, last one,
    Unknown visitor
    Unknown visitor1 times, last one,
    195 more bugmates