camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-12045) Iterator Expiration error in camel-kinesis components if the processor in route takes beyond 5 minutes to process the previously read message
Date Tue, 28 Nov 2017 18:10:00 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-12045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16269176#comment-16269176
] 

Claus Ibsen commented on CAMEL-12045:
-------------------------------------

You are welcome to dive into the source code and see if you can improve something.


> 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
>              Labels: kinesis
>
> 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)

Mime
View raw message