Thanks, that worked. But only if setting sessionTransacted to true and
not using an external transaction manager, which rules out XA transactions.
I'm still unconvinced that implementing the redelivery policy in the
MessageConsumer is appropriate or even correct. If you have two
consumers on t
gt;
>
>
>
>
> Broker:
> start="true" xmlns="http://activemq.org/config/1.0";>
>
>
>
>
>
> queuePrefix="DEAD" />
>
>
At what level does the redelivery policy get applied? I've got a
transactional consumer (Spring MDP) that is performing a rollback and I
am expecting the message to be redelivered a maximum number of times as
specified on the connection factory's redelivery policy. After the
maximum retry attem
