I believe the virtualTopicConsumerWildcards stuff only applies for Openwire protocol clients (i.e ActiveMQ 5.x), as used in the example you referenced.
Your description and log snippets note you are trying to use that with the Artemis Core JMS client instead, meaning those bits just dont apply. You should use the JMS 2 APIs for creating shared subscriptions to create+consume from new shared subscription backing queues, or alternatively you could use an FQQN address with a Topic subscriber. (Obligatory note that 2.19.1 is already an older release at this point, and there won't be any more 2.19.x releases. Aside, the next JDK LTS, 21, is due for RC1 next week...previously with JDK17, RC1 became the GA). On Tue, 1 Aug 2023 at 21:12, PAS Filip <filip....@sodexo.com.invalid> wrote: > > Hello, > > I'm running into a strange issue I cannot explain and was hoping someone > could shed some light on the issue. > > I'm running an artemis broker 2.28.0 using the artemis jms client 2.19.1 (the > latest java 8 compatible client, my client must be java 8 unfortunately). > > I've created a broker using all standard settings and copied the broker > configuration from the openwire virtual topic example, specifically the > acceptor and the topic configuration: > > <acceptor > name="artemis">tcp://0.0.0.0:61616?virtualTopicConsumerWildcards=Consumer.*.%3E%3B2</acceptor> > > <addresses> > <address name="VirtualTopic.Orders"> > <multicast/> > </address> > </addresses> > > If I copy the code from the virtual topic example into my project and run it > the test fails. > The message sent to VirtualTopic.Orders is not delivered to the consumer of > the Consumer.A.VirtualTopic.Orders destination. > The destination Consumer.A.VirtualTopic.Orders is created as a queue and is > visible as a separate address and not visible under the topic in the console. > In the log I found this message: > > DEBUG o.a.activemq.artemis.core.client - The queue > Consumer.A.VirtualTopic.Orders was created automatically. > > To make the example work I changed the configuration in the broker.xml to: > > <address name="VirtualTopic.Orders"> > <multicast> > <queue name="Consumer.A.VirtualTopic.Orders" > /> > </multicast> > </address> > > The log statement then disappears, and the behaviour is as expected. > > I'm trying to figure out where this difference in behaviour comes from. > Is there something in the maven plugin used to bootstrap the broker for the > test that does some additional configuration that would change this behaviour? > > In my use case we need to get this configuration working with the > <multicast/> tag so we can add additional queues that will receive the > messages from the topic > Without having to predefine them all in the configuration. > > > Anyone have any ideas or suggestions that would greatly be appreciated. > > Regards, > > Filip > >
