Willem, thank you for your response - although I'm sorry, I don't fully
understand it.
I have a transacted route that pulls a msg from activemq and sends it to
another route that multicasts that message to a variety of services. If any
of those services throw an exception I want to leave the msg on the queue
and try again for 5 times. After that I want to reroute the message to a
file.
In the case above, does the org.apache.activemq.RedeliveryPolicy I have set
up (shown below) on my connection factory to activemq see that as a retry or
is that totally independent? (I thought this would be considered one retry)
<bean id="jmsRedeliverPolicy" class="org.apache.activemq.RedeliveryPolicy">
<property name="maximumRedeliveries" value="5"/>
<property name="initialRedeliveryDelay" value="1000"/>
<property name="maximumRedeliveryDelay" value="256000"/>
<property name="useExponentialBackoff" value="true"/>
<property name="backOffMuliplier" value="2"/>
</bean>
In other words, could the camel redelivery policy roll back the transaction
20 times and the above redelivery policy not kick in?
Thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/Using-Dead-letter-channel-with-ActiveMQ-tp5723865p5723962.html
Sent from the Camel - Users mailing list archive at Nabble.com.
