[
https://issues.apache.org/jira/browse/CAMEL-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626851#comment-14626851
]
Ben O'Day edited comment on CAMEL-8971 at 7/14/15 7:51 PM:
-----------------------------------------------------------
attached a potential patch to get this repo to work for the simple size based
aggregation route...still investigating
[~alexlomov] - I noticed you contributed the original
HazelcastAggregationRepository...any thoughts on this?
was (Author: boday):
attached a potential patch to get this repo to work for the simple size based
aggregation route...still investigating
> 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)
