On Tue, Dec 15, 2009 at 11:08 AM, mcrive <mcr...@optasportsdata.com> wrote: > > when the exchange hits the aggregationStrategy the header is no longer set. >
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); > > > Claus Ibsen-2 wrote: >> >> >> 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-tp26780214p26792420.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
