java.lang.IllegalArgumentException: Unexpected response body offset of 76829. The way this class works, it assumes the HTTP headers are in buffer: 65536

JIRA | (sourceforge) | 1 decade ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    Hi, this night, I've got a Heritrix alert which I do not understand, honestly. As far as I see, it has to do something with ReplayCharSequenceFactory's implementation-specific treatment of a response's offset to its message body (variable "responseBodyStart"). Is this somehow related to bugs #1155641 and #922080? Perhaps you can explain what's going wrong. All the best, Christian Title: Problem occured processing 'http://www.schoenen-dunk.de/basketball/bbl/statistiken.php?action=results& file=ligasued0405.l98&endtab=30&st=30&tabtype=4' Time: Mai. 27, 2005 00:10:38 GMT Level: SEVERE Message: Problem java.lang.IllegalArgumentException: Unexpected response body offset of 76829. The way this class works, it assumes the HTTP headers are in buffer: 65536 occured when trying to process 'http://www.schoenen-dunk.de/basketball/bbl/statistiken.php?action=results& file=ligasued0405.l98&endtab=30&st=30&tabtype=4' at step PROCESSING in ExtractorHTML Associated Throwable: java.lang.IllegalArgumentException: Unexpected response body offset of 76829. The way this class works, it assumes the HTTP headers are in buffer: 65536 Message: Unexpected response body offset of 76829. The way this class works, it assumes the HTTP headers are in buffer: 65536 Stacktrace: java.lang.IllegalArgumentException: Unexpected response body offset of 76829. The way this class works, it assumes the HTTP headers are in buffer: 65536 at org.archive.io.ReplayCharSequenceFactory.checkParameters(ReplayCharSequence Factory.java:209) at org.archive.io.ReplayCharSequenceFactory.getReplayCharSequence(ReplayCharSe quenceFactory.java:124) at org.archive.io.RecordingOutputStream.getReplayCharSequence(RecordingOutputS tream.java:416) at org.archive.io.RecordingInputStream.getReplayCharSequence(RecordingInputStr eam.java:291) at org.archive.util.HttpRecorder.getReplayCharSequence(HttpRecorder.java:299) at org.archive.crawler.extractor.ExtractorHTML.innerProcess(ExtractorHTML.java :432) at org.archive.crawler.framework.Processor.process(Processor.java:103) at org.archive.crawler.framework.ToeThread.processCrawlUri(ToeThread.java:283) at org.archive.crawler.framework.ToeThread.run(ToeThread.java:152)

    JIRA | 1 decade ago | (sourceforge)
    java.lang.IllegalArgumentException: Unexpected response body offset of 76829. The way this class works, it assumes the HTTP headers are in buffer: 65536

    Root Cause Analysis

    1. java.lang.IllegalArgumentException

      Unexpected response body offset of 76829. The way this class works, it assumes the HTTP headers are in buffer: 65536

      at org.archive.io.ReplayCharSequenceFactory.checkParameters()
    2. webarchive-commons
      HttpRecorder.getReplayCharSequence
      1. org.archive.io.ReplayCharSequenceFactory.checkParameters(ReplayCharSequenceFactory.java:209)
      2. org.archive.io.ReplayCharSequenceFactory.getReplayCharSequence(ReplayCharSequenceFactory.java:124)
      3. org.archive.io.RecordingOutputStream.getReplayCharSequence(RecordingOutputStream.java:416)
      4. org.archive.io.RecordingInputStream.getReplayCharSequence(RecordingInputStream.java:291)
      5. org.archive.util.HttpRecorder.getReplayCharSequence(HttpRecorder.java:299)
      5 frames
    3. org.archive.crawler
      ToeThread.run
      1. org.archive.crawler.extractor.ExtractorHTML.innerProcess(ExtractorHTML.java:432)
      2. org.archive.crawler.framework.Processor.process(Processor.java:103)
      3. org.archive.crawler.framework.ToeThread.processCrawlUri(ToeThread.java:283)
      4. org.archive.crawler.framework.ToeThread.run(ToeThread.java:152)
      4 frames