Details
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.
Attachments
Issue Links
- is related to
-
ARTEMIS-2587 ActiveMQ5-like dead letter strategy
-
- Closed
-
- links to
