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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
