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

Posted to dev@activemq.apache.org by "Marek Strejczek (JIRA)" <ji...@apache.org> on 2013/07/03 23:35:20 UTC

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

Marek Strejczek created AMQ-4616:
------------------------------------

             Summary: Message moved from ActiveMQ.DLQ to another queue can be lost
                 Key: AMQ-4616
                 URL: https://issues.apache.org/jira/browse/AMQ-4616
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.8.0
            Reporter: Marek Strejczek


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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira