activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marek Strejczek (JIRA)" <>
Subject [jira] [Commented] (AMQ-4616) Message moved from ActiveMQ.DLQ to another queue can be lost
Date Wed, 03 Jul 2013 21:37:21 GMT


Marek Strejczek commented on AMQ-4616:

Workaround exists:
Don't use web console 'move' option to replay a message from ActiveMQ.DLQ. Use a combination
of 'copy' + 'delete' instead - delete only after confirming that the message has been processed
successfully by the consumer.
> Message moved from ActiveMQ.DLQ to another queue can be lost
> ------------------------------------------------------------
>                 Key: AMQ-4616
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.8.0
>            Reporter: Marek Strejczek
>            Priority: Minor
> This is the same issue as
> ---
> 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:

View raw message