Impelement timeout aware aggregation strategy On Wed, Apr 27, 2016 at 12:32 PM, ravi21588 <[email protected]> wrote: > Hi All, > > Iam calling two different endpoints with delimeter seperated,Parallel > Processing and timeout as 3000 ms in recipient list. > > I have mentioned aggregation strategy to aggregate the response message. > > I need to frame a fault message when iam not getting response from both the > end points. > > i thought of handling time out it in catch block,but it is not coming to > catch block insted it is processing further without aggregation with a > warning message as below. > > I could have kept a property and handled it but, Can you please tell me the > best way to handle it. > > > > > 12:20:14,715 WARN [org.apache.camel.processor.MulticastProcessor] (Camel > (camel-34) thread #118 - RecipientList-AggregateTask) Parallel processing > timed out after 3000 millis for number 0. This task will be cancelled and > will not be aggregated. > > > Route: > > <route> > <from uri="switchyard://BIHAsyncRequestService"/> > <doTry> > <log message="BIHAggregatorService - message received: > ${body}"/> > <process ref="CreateRecipientList"/> > <recipientList delimiter="," parallelProcessing="true" > strategyRef="Aggregator" timeout="3000"> > <header>A1_RECIPIENTLIST_HEADER</header> > </recipientList> > <log message="after recipient list1 - Error "/> > <doCatch> > <exception>java.lang.Exception</exception> > <log message="BIHAggregatorService - Error "/> > </doCatch> > > </doTry> > </route> > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Handling-timeout-in-Recipient-list-with-aggregation-statergy-tp5781786.html > Sent from the Camel - Users mailing list archive at Nabble.com.
-- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
