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

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.20.1
• Component/s: camel-aws
• Labels: kinesis

Environment

linux

• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Jeffrey
• Created: 28/Nov/17 16:27
• Updated: 02/Sep/22 10:59
• Resolved: 02/Sep/22 10:59

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?