On Mon, Dec 14, 2009 at 11:30 PM, mcrive <mcr...@optasportsdata.com> wrote:
>
> I am using Camel 2.2 (rev 890454)
>
> How is it possible to know if an exchange has exceeded the
> maximumRedeliveries configured on the route by using aggregationStrategy and
> if it hasn't how many redelivery have been attempted?
>
> route sample:
>
> from("direct:delivery.notification.test")
> .onException(Exception.class).maximumRedeliveries(2).redeliverDelay(60L).handled(true).end()
> .recipientList(header("recipientListHeader").tokenize(","))
> .parallelProcessing().executorService(customThreadPoolExecutor)
> .aggregationStrategy(new recipientAggregationStrategy())
> .to("direct:chunk.completed");
>See section - Redelivery header http://camel.apache.org/dead-letter-channel.html These headers apply also for the default error handler in Camel 2.x. > > -- > View this message in context: > http://old.nabble.com/recipientList-%2B-aggregationStrategy%2C-maximumRedeliveries-exceeded-tp26780214p26780214.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
