On Tue, Dec 15, 2009 at 11:37 AM, mcrive <mcr...@optasportsdata.com> wrote:
>
> even without indicating that I am handling the exception it doesn't reach the
> aggregationStrategy
>
> from("jms-test:queue:queue.delivery.notification.test").process(processor)
> .onException(Exception.class).maximumRedeliveries(2).redeliverDelay(60L).end()
> .recipientList(header("recipientListHeader").tokenize(","))
> .parallelProcessing().executorService(customThreadPoolExecutor)
> .aggregationStrategy(new RecipientAggregationStrategy())
> .to("direct:chunk.completed");
>Works fine for me, see this unit test http://svn.apache.org/viewvc?rev=890762&view=rev And remember to put .onException in the start of the route, or as a global error handler. Check out the error handling documentation at the wiki pages http://camel.apache.org/error-handling-in-camel.html Or consider checking out chapter 5 in this book http://www.manning.com/ibsen/ > > > > > Claus Ibsen-2 wrote: >> >> Dont do this as you indicate that you handle the exception, which you >> dont want to do since you want the exception to be present in the AS. >> >> .onException(Exception.class).maximumRedeliveries(2).redeliverDelay(60L).handled(true).end() >> >> But just configure it with the redelivery policies, which then on >> exhaustion will propagate it back to the AS. >> .onException(Exception.class).maximumRedeliveries(2).redeliverDelay(60L); >> > > -- > View this message in context: > http://old.nabble.com/recipientList-%2B-aggregationStrategy%2C-maximumRedeliveries-exceeded-tp26780214p26792712.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
