You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Piotr Klimczak (Jira)" <ji...@apache.org> on 2020/03/10 00:04:00 UTC
[jira] [Issue Comment Deleted] (ARTEMIS-2649) Auto-create DLQ
doesn't seem to work for JMS addresses
[ https://issues.apache.org/jira/browse/ARTEMIS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Klimczak updated ARTEMIS-2649:
------------------------------------
Comment: was deleted
(was: It is not queue name a problem- I have added prefix to queue name and the message is still not popping up in queue inside of DLQ address. I can see however prefixed queue created in DLQ address.
Regardless of above it is still intriguing how JMS client will behave in this scenario, will it consume from DLQ queue with the same name?)
> 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)