[
https://issues.apache.org/jira/browse/CAMEL-12668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554378#comment-16554378
]
Chirag Anand commented on CAMEL-12668:
--------------------------------------
[~dmvolod] I have tried the same scenario with camel-stream component using the
same aggregation logic. It succeeded for version 2.16.2 but when i am using
2.17.0 it fails again. The route i am using is as follows -
from("stream:file?fileName=C:/Test/ABC.txt")
.aggregate(constant(true), new CamelAggregator()).completionSize(50)
.forceCompletionOnStop().process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
List<Object> statusObjects =
exchange.getIn().getBody(List.class);
System.out.println(statusObjects.size());
}
}).end();
Can we please fix it at the earliest now? It's very important that this gets
fixed soon.
> Aggregate with forcecompleteonstop doesn't seem to be honored
> -------------------------------------------------------------
>
> Key: CAMEL-12668
> URL: https://issues.apache.org/jira/browse/CAMEL-12668
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.17.0
> Reporter: Chirag Anand
> Priority: Major
> Fix For: 2.22.0
>
>
> I have a camel project where I am using twitter component of the camel and
> using the streaming/filter endpoint. The route is something like
> from(<twitterstreamendpoint>).aggregate(<customstratergy>).completionSize().forceCompletionOnStop().process().
> The problem here is when I stop the context the remaining aggregated
> exchanges are not being flushed to the processor. Earlier I was using version
> 2.16.2 and it worked fine, but with the latest release i.e 2.22.0 I am facing
> this issue. The configuration hasn’t changed a bit. To be certain i tried it
> with version 2.17.0 also, doesn't work either.
>
> I tried debugging and I noticed at somepoint there is a
> RejectedExecutionException, not sure why because there is no change in the
> configuration.
>
> Can you please resolve this at the earliest? or at least tell me if there has
> been any change in the functionality/usage?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
