You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "David Whitney (Jira)" <ji...@apache.org> on 2022/09/09 13:07:00 UTC

[jira] [Created] (ARTEMIS-3979) Change in behavior when dynamically creating queue based on FQQN for Openwire clients

David Whitney created ARTEMIS-3979:
--------------------------------------

             Summary: Change in behavior when dynamically creating queue based on FQQN for Openwire clients
                 Key: ARTEMIS-3979
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3979
             Project: ActiveMQ Artemis
          Issue Type: Bug
          Components: ActiveMQ-Artemis-Native
    Affects Versions: 2.24.0, 2.19.1
            Reporter: David Whitney
            Assignee: Clebert Suconic
         Attachments: broker.xml

When using Apache Artemis 2.18.0, I can successfully create a consumer queue using a FQQN (e.g., MyTopic::MQ1) and receive messages from it.

The consumer performs this:
{code:java}
...
cms::Destination* dest = session->createQueue(fqqn_topic);
cms::MessageConsumer* consumer = session.createConsumer(dest);
...
TopicListener* listener = new TopicListener(...);   // a subclass of cms::MessageListener
consumer->setMessageListener(listener);

{code}
My test application creates two consumers subscribed using an FQQN topic, and a single producer that issues 10 messages. I expect each consumer to receive 5 messages each, in a 'ping-pong' manner.

The test works flawlessly with Artemis 2.18.0, however if I upgrade to later versions, the test sometimes runs successfully, and at other times, the consumer does not receive any messages, thus resulting in a failed test.

I cannot ascertain if this is an issue with the creation/usage of a dynamically created queue, or perhaps something to do with the delivery of messages to the MessageListener.

It is quite obvious that something has changed between Artemis 2.18.0 and 2.19.1. Hopefully this issue can be fixed, or perhaps a guidance can be offered to indicate whether I need to tweak my broker's configuration file (which I have attached).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)