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");
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.
