[
https://issues.apache.org/jira/browse/ARTEMIS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517292#comment-16517292
]
Justin Bertram commented on ARTEMIS-1933:
-----------------------------------------
Thanks for the additional information. I believe your issue is due to a
misconfiguration in your {{broker.xml}}. You indicate you're using the
configuration from ARTEMIS-1906, but you don't have this:
{code:xml}
<wildcard-addresses>
<delimiter>/</delimiter>
</wildcard-addresses>
{code}
I believe this is preventing your address settings from being applied properly
in this case so that both queues get the default {{MULTICAST}} routing and
therefore both receive the message. I mimicked your test and configuration in
a test of my own which failed. Once I added the proper {{delimiter}} the test
passed.
> 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)
