Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-12045

Iterator Expiration error in camel-kinesis components if the processor in route takes beyond 5 minutes to process the previously read message

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.20.1
    • Fix Version/s: None
    • Component/s: camel-aws
    • Labels:
    • Environment:

      linux

    • Estimated Complexity:
      Unknown

      Description

      The camel kinesis components throws an iterator expired exception when the processor took more than five minutes to process the previous record received from the stream. Such similar fix has been already done for ddbstream(https://fisheye.apache.org/changelog/camel-git?cs=258f9c9ca808d6f97eced2b0b42db4e2cc5463f4). Will a similar fix works for kinesis component as well or the issue can be handled in a different way?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jeffrey550@gmail Jeffrey
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: