[
https://issues.apache.org/jira/browse/ARTEMIS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055692#comment-17055692
]
Piotr Klimczak commented on ARTEMIS-2649:
-----------------------------------------
Thanks for your answer [~jbertram],
The exact way to reproduce the problem is described in 2nd comment. I've been
editing comments multiple times, so apologies if that caused confusion.
So the issue happens when you move messages between queues in web console as
then _AMQ_ORIG_ADDRESS has the value of original address and not the moved to
address.
As for ARTEMIS-2587 I think that one of the requirements should be that under
no circumstances, you can actually lose a message.
So with current implementation you will, as described above.
I understand that this is can be considered "exotic" situation, however it
useful in some support cases when support team must deal with some
misconfiguration issue and they need to move messages between destinations.
I've seen it few times already.
> Auto-create DLQ doesn't seem to work for JMS addresses
> ------------------------------------------------------
>
> 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.
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
