[
https://issues.apache.org/jira/browse/ARTEMIS-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389638#comment-15389638
]
ASF GitHub Bot commented on ARTEMIS-548:
----------------------------------------
Github user mtaylor commented on the issue:
https://github.com/apache/activemq-artemis/pull/653
From looking at the code I believe normal subscription queues are not
encapsulated via connection and instead are global. Specifically, the
subscription queue name is based on the subscription id. This is only unique in
the context of the connection. Another connection could specify the same
subscription id for something else completely.
This could result in:
1. Client 2 receives messages from the wrong address.
2. Client 1 unsubscribe deletes Client 2 subscription queue.
3. When both addresses are the same, p2p semantics instead of pub/sub.
> Add STOMP-based ability to delete durable subscriber
> ----------------------------------------------------
>
> Key: ARTEMIS-548
> URL: https://issues.apache.org/jira/browse/ARTEMIS-548
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 1.2.0
> Reporter: Justin Bertram
> Assignee: Justin Bertram
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
