[jira] [Commented] (CAMEL-8971) HazelcastAggregatorRepository redelivers incorrectly
[
https://issues.apache.org/jira/browse/CAMEL-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894322#comment-15894322
]
Claus Ibsen commented on CAMEL-8971:
The aggregation strategy should favor returning the oldExchange - we had an
issue in the jdbc repo. Now Camel logs a WARN if you return the wrong instance.
> HazelcastAggregatorRepository redelivers incorrectly
>
>
> Key: CAMEL-8971
> URL: https://issues.apache.org/jira/browse/CAMEL-8971
> Project: Camel
> Issue Type: Bug
> Components: camel-hazelcast
>Affects Versions: 2.14.1
>Reporter: Ben O'Day
>Priority: Minor
> Attachments: HazelcastAggRepo-redelivery-fix.patch
>
>
> seeing an incorrect redelivery of a message when using the
> UseLatestAggregationStrategy...
> this very basic route (see attached)...
> from("direct:start")
> .aggregate(constant(true), new
> UseLatestAggregationStrategy())
> .completionSize(2)
>
> .aggregationRepository(repo)
> .to("mock:mock");
> resulting in a duplicate message being processed through the aggregator
> route...
> if the default in-memory repo is used, the test behaves as expected...no
> unnecessary redelivery, etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CAMEL-8971) HazelcastAggregatorRepository redelivers incorrectly
[ https://issues.apache.org/jira/browse/CAMEL-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14636915#comment-14636915 ] Ben O'Day commented on CAMEL-8971: -- [~alexlomov] - not sure I follow how this disables recovery, can you clarify? either way, this very basic unit test using the Hazelcast repo fails w/o my (or some other) changes...any thoughts on how to address the root cause of the issue otherwise? HazelcastAggregatorRepository redelivers incorrectly Key: CAMEL-8971 URL: https://issues.apache.org/jira/browse/CAMEL-8971 Project: Camel Issue Type: Bug Components: camel-hazelcast Affects Versions: 2.16 Reporter: Ben O'Day Assignee: Ben O'Day Priority: Minor Attachments: HazelcastAggRepo-redelivery-fix.patch seeing an incorrect redelivery of a message when using the UseLatestAggregationStrategy... this very basic route (see attached)... from(direct:start) .aggregate(constant(true), new UseLatestAggregationStrategy()) .completionSize(2) .aggregationRepository(repo) .to(mock:mock); resulting in a duplicate message being processed through the aggregator route... if the default in-memory repo is used, the test behaves as expected...no unnecessary redelivery, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8971) HazelcastAggregatorRepository redelivers incorrectly
[ https://issues.apache.org/jira/browse/CAMEL-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14633159#comment-14633159 ] Alexander Lomov commented on CAMEL-8971: As I see the only thing the patch does is disabling recovery despite of the RecoverableAggregationRepository settings. I believe it's not the desired solution. I've noticed LevelDBAggregationRepository in your tests fails to confirm an exchange is done. I guess it's the problem. HazelcastAggregatorRepository redelivers incorrectly Key: CAMEL-8971 URL: https://issues.apache.org/jira/browse/CAMEL-8971 Project: Camel Issue Type: Bug Components: camel-hazelcast Affects Versions: 2.16 Reporter: Ben O'Day Assignee: Ben O'Day Priority: Minor Attachments: HazelcastAggRepo-redelivery-fix.patch seeing an incorrect redelivery of a message when using the UseLatestAggregationStrategy... this very basic route (see attached)... from(direct:start) .aggregate(constant(true), new UseLatestAggregationStrategy()) .completionSize(2) .aggregationRepository(repo) .to(mock:mock); resulting in a duplicate message being processed through the aggregator route... if the default in-memory repo is used, the test behaves as expected...no unnecessary redelivery, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
