[
https://issues.apache.org/jira/browse/ARTEMIS-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-855.
------------------------------------
Resolution: Fixed
I'm pretty sure this is done already. Any protocol can use a queue where
`exclusive="true"`. We can't do anything about the URL which protocols like
MQTT, AMQP, and STOMP use because those are standardized and anybody can
implement a client.
> Support exclusive consumer over non-JMS protocols
> -------------------------------------------------
>
> Key: ARTEMIS-855
> URL: https://issues.apache.org/jira/browse/ARTEMIS-855
> Project: ActiveMQ Artemis
> Issue Type: Sub-task
> Components: Broker
> Reporter: Matt Pavlovich
> Priority: Major
>
> STOMP, MQTT, AMQP, etc.
> This is often needed by users in ActiveMQ 5.x. but not fully supported.
> Suggested implementation: use a URI parameter that is consistent across all
> protocols
> mqtt url: tcp://....:188?exclusiveConsumer=true
> amqp url: tcp://... :5762?exclusiveConsumer=true
> etc..
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
