On Tue, Dec 15, 2009 at 11:37 AM, mcrive 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).redeliverDel
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").
On Tue, Dec 15, 2009 at 11:08 AM, mcrive 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.cla
when the exchange hits the aggregationStrategy the header is no longer set.
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 cont
On Mon, Dec 14, 2009 at 11:30 PM, mcrive 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 samp
