Re: Aggregator issue

2021-11-19 Thread Jeremy Ross
Your diagram came across jumbled, so hard for me to read it. But your AggregationStrategy is responsible for handling and/or propagating exceptions. If it swallows an exception, and doesn't pass it on via the "newExchange", it won't be available to the route's error handler. On Fri, Nov 19, 2021 a

Aggregator issue

2021-11-19 Thread Laurent Lamouline
Hello, I'm currently facing an issue when using the Aggregator component in a processing flow. The processing flow is as follows : |---| | Main route entry point | |

Re: Camel Aggregator issue

2017-01-06 Thread Steve973
leName} > > > > > > > > The SQL is like: > select * from MESSAGES M where -any condition- order by M.MESSAGE_FORMAT_ID > > > I will always get a list of Messages, ordered by the MFO ID. > > > -- > O

Re: Camel Aggregator issue

2017-01-04 Thread okieven
://camel.465427.n5.nabble.com/Camel-Aggregator-issue-tp5792131p5792145.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Aggregator issue

2017-01-04 Thread Steve973
I could count the number of Messages for each ID, but in respect of > performance it´s not the best solution for me. > > -- > Oliver > > > > -- > View this message in context: http://camel.465427.n5.nabble. > com/Camel-Aggregator-issue-tp5792131p5792143.html > Sent from the Camel - Users mailing list archive at Nabble.com. >

Re: Camel Aggregator issue

2017-01-04 Thread okieven
Hi Steve, thanks for your answer. I could count the number of Messages for each ID, but in respect of performance it´s not the best solution for me. -- Oliver -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Aggregator-issue-tp5792131p5792143.html Sent from the Camel

Re: Camel Aggregator issue

2017-01-04 Thread Steve973
ible > completion condition in your example? > The list is always ordered by MFO ID, but the number of Messages for each > MFO ID is always different. > > > -- > Oliver > > > > -- > View this message in context: http://camel.465427.n5.nabble. > com/Camel-Agg

Re: Camel Aggregator issue

2017-01-04 Thread okieven
context: http://camel.465427.n5.nabble.com/Camel-Aggregator-issue-tp5792131p5792141.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Aggregator issue

2017-01-04 Thread Jakub Korab
message in context: http://camel.465427.n5.nabble.com/Camel-Aggregator-issue-tp5792131.html Sent from the Camel - Users mailing list archive at Nabble.com.

Camel Aggregator issue

2017-01-04 Thread okieven
tried a lot of configurations, wrote my own aggregator etc, but nothing worked fine for me. How can I achieve this? Thanks, Oliver -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Aggregator-issue-tp5792131.html Sent from the Camel - Users mailing list archive at

Re: aggregator issue

2012-11-30 Thread Claus Ibsen
On Thu, Nov 29, 2012 at 12:09 PM, Jason Chaffee wrote: > I have a custom aggregator strategy but for some reason the oldExchange is > always null. Any ideas? > > > Here is my route. > > from("seda:Split") > .routeId("Split") > .aggregate(new MyAggregationStrategy()) > .c

Re: aggregator issue

2012-11-30 Thread Henryk Konsek
> I want to merge the message bodies into a container object. I would use GroupedExchangeAggregationStrategy and then forward the results of the aggregation to the processor. from("direct:aggregateMe"). aggregate(constant(true),new GroupedExchangeAggregationStrategy()). completionSize(2). .

Re: aggregator issue

2012-11-29 Thread Jason Chaffee
I really don't want grouped exchanges, that is if I understand them correctly. I want to merge the message bodies into a container object. In a nutshell, I am loading a third-party XML file, splitting it into individual items, normalizing those items into my objects, and then I want to aggregate

Re: aggregator issue

2012-11-29 Thread Henryk Konsek
Hi Jason, > Here is my AggregationStrategy: Your custom aggregation strategy acts like GroupedExchangeAggregationStrategy. Why don't use the latter then? from("direct:aggregateMe"). aggregate(constant(true),new GroupedExchangeAggregationStrategy()). completionSize(2). .setBody(property(Exc

Re: aggregator issue

2012-11-29 Thread Jason Chaffee
Same issue. By the way, here is my route sends the split message to the "seda:split". from("file://./target/?fileName=raw.xml") .routeId("FileIngest") .split() .tokenizeXML("offer") .parallelProcessing() .streaming() .unmarshal().jaxb("com.otherCompany.ingest.model"

Re: aggregator issue

2012-11-29 Thread Charles Moulliard
Do you observe the same behavior if you start your camel route with direct component (from("direct:a")) ? On Thu, Nov 29, 2012 at 6:47 PM, Jason Chaffee wrote: > It is doesn't complete until after some 20,000 calls, I confirmed that is > correct. However, the oldEchange is null for every single

Re: aggregator issue

2012-11-29 Thread Jason Chaffee
It is doesn't complete until after some 20,000 calls, I confirmed that is correct. However, the oldEchange is null for every single one of them. On 11/29/12 4:22 AM, "Claus Ibsen" wrote: >oldExchange is null on the 1st call. > >Maybe you completion triggers because there is only 1 exchange in

Re: aggregator issue

2012-11-29 Thread Claus Ibsen
oldExchange is null on the 1st call. Maybe you completion triggers because there is only 1 exchange in the batch. On Thu, Nov 29, 2012 at 12:09 PM, Jason Chaffee wrote: > I have a custom aggregator strategy but for some reason the oldExchange is > always null. Any ideas? > > > Here is my rou

aggregator issue

2012-11-29 Thread Jason Chaffee
I have a custom aggregator strategy but for some reason the oldExchange is always null. Any ideas? Here is my route. from("seda:Split") .routeId("Split") .aggregate(new MyAggregationStrategy()) .constant(true) .completionFromBatchConsumer() .completionP