[
https://issues.apache.org/jira/browse/ARTEMIS-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900911#comment-16900911
]
Anton Roskvist commented on ARTEMIS-2356:
-----------------------------------------
That's too bad, as this behavior is contrary to how ActiveMQ 5 handles the same
situation. Any chance this might become a feature toggle at some point?
> Wildcard routing not working as expected
> ----------------------------------------
>
> Key: ARTEMIS-2356
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2356
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.8.1
> Reporter: Anton Roskvist
> Priority: Major
>
> I am trying to set up a consumer to listen to several queues using a
> wildcard. What I am expecting to happen is that ActiveMQ Artemis forwards
> messages from queues matching the wildcard to the consumer.
> The messages are indeed sent to the consumer, but all original messages stay
> in their respective queues as well. Also, this only works for messages coming
> in _after_ the consumer is connected, any preexisting messages remain
> undelivered.
> I have been able to reproduce this in a broker without any changes made to
> it's configuration.
> To reproduce:
> Download and install the latest version (or any I have tested so far) of
> Apache Artemis.
> Send messages to a few queues, say:
> ARTEMIS.WILDCARD.1
> ARTEMIS.WILDCARD.2
> ARTEMIS.WILDCARD.3
> Set up a consumer to listen to
> ARTEMIS.#
> No messages will get delivered to consumer.
> Send more messages to the aforementioned queues.
> These are received, but are also added to the original queues.
>
> I am using the Openwire protocol for both Producers and Consumers and this is
> part of a migration from the old ActiveMQ 5 broker to Artemis. This works as
> expected on the old ActiveMQ-broker.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
