[jira] [Comment Edited] (ARTEMIS-2356) Wildcard routing not working as expected

["Justin Bertram (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16901153#comment-16901153 ] 

Justin Bertram edited comment on ARTEMIS-2356 at 8/6/19 3:15 PM:
-----------------------------------------------------------------

As noted on ARTEMIS-2375 the 5.x implementation is a wildcard *consumer* and the Artemis implementation is a wildcard *address*. The different designs lead to some differences in behavior each with pros & cons. Given the underlying design I don't see how the wildcard address implementation in Artemis could ever be configured to yield the exact behavior of a wildcard consumer (and vice versa). Providing the exact same semantics would require a fresh wildcard consumer implementation.

For many use-cases it may be possible to get "close enough" (e.g. if you don't want messages to accumulate in the individual queues which are covered by the wildcard then just remove the queues and leave the addresses or if you want to receive messages sent before the consumer connects using the wildcard then statically create the wildcard address). However, you don't provide enough details to know if any such adjustments would be feasible for your use-case.


was (Author: jbertram):
As noted on ARTEMIS-2375 the 5.x implementation is a wildcard *consumer* and the Artemis implementation is a wildcard *address*. The different designs lead to some differences in behavior each with pros & cons. Given the underlying design I don't see how the wildcard address implementation in Artemis could ever be configured to yield the exact behavior of a wildcard consumer (and vice versa). Providing the exact same semantics would require a fresh wildcard consumer implementation.

For many use-cases it may be possible to get "close enough" (e.g. if you don't want messages to accumulate in the individual queues which are covered by the wildcard then just remove the queues and leave the addresses or if you want to receive messages sent before the consumer connects using the wildcard address then statically create the wildcard address). However, you don't provide enough details to know if any such adjustments would be feasible for your use-case.

> 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)