[AMQ-4616] Message moved from ActiveMQ.DLQ to another queue can be lost

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 5.8.0
• Fix Version/s: 5.9.0
• Assignee: Unassigned
• Reporter: Marek Strejczek
• Created: 03/Jul/13 21:34
• Updated: 05/Jul/13 13:12
• Resolved: 05/Jul/13 13:12

Description

This is the same issue as https://fusesource.com/issues/browse/ENTMQ-341.

—

A persistent message can be lost by the broker.
How to reproduce:
1. Put a persistent message onto queue A.
2. A consumer (using XA transactions) receives the message. The consumer always throws an exception, so after predefined number of redelivery attempts the message goes to ActiveMQ.DLQ.
3. Using web console move the message from ActiveMQ.DLQ back to queue A.
4. Consumer receives the message and again throws exceptions in its onMessage method.
4a. Expected behaviour: message lands on ActiveMQ.DLQ again.
4b. Actual behaviour: message dissappears - it's neither on queue A nor ActiveMQ.DLQ.

Issue Links

• duplicates: AMQ-3405 DLQ messages moved/copied into original queue disappear after failing processing for a second time