[
https://issues.apache.org/jira/browse/ARTEMIS-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501014#comment-16501014
]
Robbie Gemmell commented on ARTEMIS-1618:
-----------------------------------------
Yep, using the client-side redelivery enforcement along with recover() (which
is performed client-side to satisfy JMS stated ordering behaviour) but then
specifically telling it to RELEASE in this way is really quite odd, leading it
to repeat. Leaving the outcome configuration at its default will lead the
server side delivery count to increment, and so is more likely to give you
behaviour as you desire.
> DeadLettering on AMQP ignores maxDeliveryAttempts endlessly redelivering of
> released messages
> ---------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-1618
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1618
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP, Broker
> Affects Versions: 2.4.0, 2.6.0
> Environment: Artemis 2.6.0
> Reporter: Johan Stenberg
> Priority: Major
> Attachments: Artemis1618_AmqpDeadLettering_Test.java
>
>
> A rejected message gets infinitely redelivered, even if maxDeliveryAttempts
> and dead letter queue are specified.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
