My mistake - its not really working. There is no notification message. The retry works but the exception strategy fails. After the set number of retries nothing happens. The exception strategy on the base connector is being set but never gets called. The expected exception gets logged but I just can't get a message routed with the exception in it.
It looks like I should have stuck to hand coded retries.
Thanks for the help, this is working now.
I made a change like :
<spring:bean name="redeliveryPolicy" class="org.apache.activemq.RedeliveryPolicy">
<spring:property name="initialRedeliveryDelay" value="5000"/>
<spring:property name="maximumRedeliveries" value="3"/>
</spring:bean>
The max redeliveries on the AMQ connector didnt seem to work. Plus added in the transaction on the endpoint.
UWD wrote:
Don't think it's possible to get redelivering functionality without transaction support.
When you do a rollback(for example throw an exception from code) the transaction will be rolled back, and then the redelivery will be done.
