You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/03/13 18:46:00 UTC
[jira] [Work logged] (ARTEMIS-2649) Auto-create DLQ message loss
when moving messages between destinations
[ https://issues.apache.org/jira/browse/ARTEMIS-2649?focusedWorklogId=403080&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-403080 ]
ASF GitHub Bot logged work on ARTEMIS-2649:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Mar/20 18:45
Start Date: 13/Mar/20 18:45
Worklog Time Spent: 10m
Work Description: jbertram commented on pull request #3017: ARTEMIS-2649 refactor ORIG message props
URL: https://github.com/apache/activemq-artemis/pull/3017
ORIG message propertes like _AMQ_ORIG_ADDRESS are added to messages
during various broker operations (e.g. diverting a message, expiring a
message, etc.). However, if multiple operations set these properties on
the same message (e.g. administratively moving a message which
eventually gets sent to a dead-letter address) then important details
can be lost. This is particularly problematic when using auto-created
dead-letter or exipry resources which use filters based on
_AMQ_ORIG_ADDRESS and can lead to message loss.
This commit implements "breadcrumb" properties so that the full history
of the message is retained and the most recent information is stored in
the original ORIG properties.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 403080)
Remaining Estimate: 0h
Time Spent: 10m
> Auto-create DLQ message loss when moving messages between destinations
> ----------------------------------------------------------------------
>
> Key: ARTEMIS-2649
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2649
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.12.0
> Environment: Centos 7 container in OKD with Java 8.
> Reporter: Piotr Klimczak
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> [~jbertram], first of all thanks a lot for ARTEMIS-2587 implementation.
> This was a must for me to switch to Artemis.
> In past I have even tried to implement it in Artermis, but having no previous experience with it, only with your PR I understood how nicely and easily it can be implemented and how much I have overcomplicated it.
> So I am testing 2.12.0 snapshot as I am really interested in work done under ARTEMIS-2587.
> I am connecting using open wire protocol using camel-jms component, having replaced old AMQ5 with Artermis.
> On failed consumption, I can see queue being created under DLQ address with multicast and filter _AMQ_ORIG_ADDRESS = 'some.queue'.
> However it is empty and message is lost.
> Reproduction scenario:
> # Sending message to address A
> # Moving message from A queue to B using web console move function
> # Consuming from B and failing consumption
> Observed state:
> # Queue is being created
> # Message is lost and logs are not indicating anything
> As a result this message being moved from A to be B queue, the header "_AMQ_ORIG_ADDRESS" has value "A" instead of "B" and therefore it does not match the filter "B" and is getting lost.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)