[
https://issues.apache.org/jira/browse/ARTEMIS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Klimczak updated ARTEMIS-2649:
------------------------------------
Description:
[~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.
was:
[~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.
So the observation is that:
# Queue is being created
# Message is lost and logs are not indicating anything
I have not debugged it yet, this is early observation.
I might do more investigation if time will allow.
> 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
>
> [~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)
