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.
Hi,
I've just tried the following but it isn't redelivering, just a single delivery attempt. Is there an obvious problem with the queue?
<jms:activemq-connector name="targetServiceConnector" maxRedelivery="3" connectionFactory-ref="amqConnectionfactory" >
<mule:default-connector-exception-strategy>
<mule:outbound-endpoint ref="operation.error"/>
</mule:default-connector-exception-strategy>
</jms:activemq-connector>
<spring:bean name="redeliveryPolicy" class="org.apache.activemq.RedeliveryPolicy">
<spring:property name="initialRedeliveryDelay" value="5000"/>
</spring:bean>
<spring:bean name="amqConnectionfactory" class="org.apache.activemq.ActiveMQConnectionFactory">
<spring:property name="redeliveryPolicy" ref="redeliveryPolicy"/>
</spring:bean>
UWD wrote:
I don't know, but maybe you can implement your own RedeliveryHandler and handle it yourself if it's not possible in any other way. Check out the docs for the JmsProvider.
