You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2021/10/02 19:30:00 UTC

[jira] [Commented] (ARTEMIS-3511) Messages stuck in queue instead of moving to DLQ

    [ https://issues.apache.org/jira/browse/ARTEMIS-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423596#comment-17423596 ] 

Justin Bertram commented on ARTEMIS-3511:
-----------------------------------------

What kind of JMS client are you using? ActiveMQ Artemis supports Qpid JMS, OpenWire JMS, and core JMS clients.

> 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
>
> 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)