activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AMQ-3405) DLQ messages moved/copied into original queue disappear after failing processing for a second time
Date Thu, 07 Jun 2018 10:40:00 GMT


ASF subversion and git services commented on AMQ-3405:

Commit 1ebf1862795286505dc2ce2d36e91008029061a3 in activemq's branch refs/heads/master from
[;h=1ebf186 ]

AMQ-3405 - rework fix to use original destination strategy which may be different from the
default shared strategy. new test

> DLQ messages moved/copied into original queue disappear after failing processing for
a second time
> --------------------------------------------------------------------------------------------------
>                 Key: AMQ-3405
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.2
>         Environment: Windows 7, Java 64bit 1.6 update 20, Client and server 5.4.2
>            Reporter: Carey Flichel
>            Assignee: Timothy Bish
>            Priority: Major
>             Fix For: 5.9.0
> 1. Message in queue A fails enough times to be moved to the DLQ.
> 2. We move/copy the message back to queue A to attempt reprocessing. Invoking the retry
operation from JMX can also be used.
> 3. The consumer once again fails to consume the message greater than the max number of
> 4. The message is not put back into the DLQ. If it was moved rather than copied, it means
we have a message that was never successfully consumed, but has nevertheless disappeared.
> This is all with the default ActiveMQ settings, though I tried adjusted the DLQ configuration
to support both expired and non-persistent messages.
> I found this posting which seems to indicate the same issue I am seeing:
One difference that I am seeing is that restarting ActiveMQ does not cause the message to
show up in the DLQ again. Once it is lost, it is lost forever.
> To replicate this, I believe you can use a consumer that just fails on every invocation.
> One interesting thing is that if I put a message into the DLQ directly, then move it
to a queue with a consumer, it will end up in the DLQ again as you would expect. If I then
move the DLQ message back to the original queue, it will then show the bevahiour outlined

This message was sent by Atlassian JIRA

View raw message