You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2021/09/23 21:05:00 UTC

[jira] [Resolved] (ARTEMIS-1933) Wildcard subscriptions deliver queue message multiple times (STOMP)

     [ https://issues.apache.org/jira/browse/ARTEMIS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram resolved ARTEMIS-1933.
-------------------------------------
    Resolution: Abandoned

> 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
(v8.3.4#803005)