[
https://issues.apache.org/jira/browse/CAMEL-19582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748278#comment-17748278
]
Hamed Hatami commented on CAMEL-19582:
--------------------------------------
[~davsclaus] For the time being , I solved my problem by stopping and starting
the camel routes and in general I suppose, connection can be used for both
consumer and producer parts and if we improve the connection part then both
functionalities can utilize the same features of connection.
I'll work on the user-story on my own for sure
> Lack of Camel aws2 Kinesis Fault-Tolerance
> ------------------------------------------
>
> Key: CAMEL-19582
> URL: https://issues.apache.org/jira/browse/CAMEL-19582
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws2
> Affects Versions: 4.0-M3
> Reporter: Hamed Hatami
> Priority: Major
>
> In "aws2-kinesis" component , there's no retry mechanism (resiliency is not
> considered) just in case there's any connectivity outage, therefore if
> Kinesis goes off , Kinesis Client won't get back to work anymore.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
