You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jeffrey (JIRA)" <ji...@apache.org> on 2017/11/28 16:28:00 UTC
[jira] [Created] (CAMEL-12045) Iterator Expiration error in
camel-kinesis components if the processor in route takes beyond 5 minutes
to process the previously read message
Jeffrey created CAMEL-12045:
-------------------------------
Summary: Iterator Expiration error in camel-kinesis components if the processor in route takes beyond 5 minutes to process the previously read message
Key: CAMEL-12045
URL: https://issues.apache.org/jira/browse/CAMEL-12045
Project: Camel
Issue Type: Bug
Components: camel-aws
Affects Versions: 2.20.1
Environment: linux
Reporter: Jeffrey
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?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)