[
https://issues.apache.org/jira/browse/ARTEMIS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520810#comment-16520810
]
Justin Bertram commented on ARTEMIS-1933:
-----------------------------------------
Thanks for the correction. I am able to confirm the behavior you're seeing.
At this point I'm trying to understand the semantic you're after as it doesn't
seem to correspond to the normal wildcard use-case. Typically when a wildcard
subscription is created it gets *all* the messages which are sent to any
matching address. This is described in the [Artemis
documentation|https://activemq.apache.org/artemis/docs/latest/wildcard-routing.html]
as well as the [ActiveMQ 5.x
documentation|http://activemq.apache.org/wildcards.html]. However, you're
indicating that you want the wildcard subscription to work like a normal
anycast queue. Is that correct? If so, what is the benefit of using the
wildcard vs. a normal subscription? Can you elaborate on the use-case for this?
> Wildcard subscriptions deliver queue message multiple times (STOMP)
> -------------------------------------------------------------------
>
> Key: ARTEMIS-1933
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1933
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Lionel Cons
> Priority: Major
> Attachments: ARTEMIS-1933.text, broker.xml
>
>
> Here is the scenario (using STOMP):
> - one subscription to {{/queue/test.foo}}
> - one subscription to {{/queue/test.*}}
> - one message sent to {{/queue/test.foo}}
> Since we are dealing with queues, the message should be load-balanced between
> the two matching subscriptions so only one should get it. This is what
> ActiveMQ 5 does.
> With Artemis, both subscriptions get the message.
> FWIW, I'm using {{default-address-routing-type}} to make sure destinations
> starting with {{/queue/}} act like a queue (see ARTEMIS-1906).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
