[
https://issues.apache.org/jira/browse/ARTEMIS-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17427790#comment-17427790
]
Justin Bertram commented on ARTEMIS-3511:
-----------------------------------------
I just tested your code in 2.18.0. Upon the second recovery the broker sent the
message to the DLQ.
> Messages stuck in queue instead of moving to DLQ
> ------------------------------------------------
>
> Key: ARTEMIS-3511
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3511
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.18.0
> Reporter: Dmitry Skorinov
> Priority: Major
> Attachments: maxredelivery.java
>
>
> The problem exists only in v2.18, v2.16 - everything is fine.
> Steps to reproduce:
> 1. create session with client_ack
> 2. get message
> 3. session.recover()
> 4. repeat until MaximumRedeliveries is reached
> 5. result: message stucks in queue (in locked state) instead of moving to
> DLQ. After server restart: message appears in queue again.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
