Hi, Maybe the issue is about the definition of the "old" exchange in the timeout method. This is the exchange that contains everything that was aggregated at the time the timeout occurs. The timeout method just gives you the opportunity to clean this data up.
Does this answer the question? Best regards Stephan -----Original Message----- From: Claus Ibsen [mailto:[email protected]] Sent: Donnerstag, 28. April 2016 10:05 To: [email protected] Subject: Re: Handling timeout in Recipient list with aggregation statergy If you enable streaming mode on recipient then the aggregate is called when the responses come back. Otherwise the aggregate is called in the same order as the recipient list endpoints, eg first recipient response, 2nd recipient response, 3rd ... N. On Thu, Apr 28, 2016 at 10:00 AM, ravi narayanan <[email protected]> wrote: > Hi Sven, > I have two endpoints set in recipient list header delimiter seperated. > I meant when i receive response from both the endpoints only then will the > aggregate method gets called,else will it call timeout method.? > > > > On Wed, Apr 27, 2016 at 10:22 PM, Sven Bauhan <[email protected]> wrote: > >> On 04/27/16 15:36, ravi narayanan wrote: >> >>> Hi Claus, >>> I tried implementing timeout aware aggregation strategy and implemented >>> timeout method in it. >>> now when ever timeout happens(complete Timeout/Partial Response) the Old >>> exchange message is coming to timeout method. >>> >> Of course it is the old exchange, as no new exchange received within the >> timeout time. >> >> will the aggregate method gets invoked only when it gets response from all >>> the endpoints? >>> >>> what do you mean with "all the endpoints"? >> >> -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
