[
https://issues.apache.org/jira/browse/CAMEL-15289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159010#comment-17159010
]
Serge Starovoitenkov commented on CAMEL-15289:
----------------------------------------------
The behavior is reproducible, but to be more precise - not all aggregation
timeouts lost but only those that were set on the node that stopped. Timeouts
set on other nodes still work. When the failed|stopped node is on again all
timeouts are also on,
> Aggregate with cluster(timeout)
> -------------------------------
>
> Key: CAMEL-15289
> URL: https://issues.apache.org/jira/browse/CAMEL-15289
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.23.0
> Reporter: Borodina Valery
> Priority: Major
>
> I used TimeoutAwareAggregationStrategy and JdbcAggregationRepository. I have
> aggregator in camel-route in cluster. When one node failed all timeout also
> lost. And I didn't lose message but I lost functional on timeout.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
