[
https://issues.apache.org/jira/browse/AMQ-9514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886608#comment-17886608
]
Ondrej Mrekaj commented on AMQ-9514:
------------------------------------
something new?
> How to set exclusive consumer for ws connector?
> -----------------------------------------------
>
> Key: AMQ-9514
> URL: https://issues.apache.org/jira/browse/AMQ-9514
> Project: ActiveMQ Classic
> Issue Type: Bug
> Environment: ActiveMQ versions 5.15.3 and 5.18.3
> Reporter: Ondrej Mrekaj
> Assignee: Jean-Baptiste Onofré
> Priority: Major
>
> Hello,
> I attempted to edit the {{broker.xml}} file as follows:
> {code:java}
> <destinationPolicy>
> <policyMap>
> <policyEntries>
> <policyEntry queue=">" allConsumersExclusiveByDefault="true"/>
> </policyEntries>
> </policyMap>
> </destinationPolicy> {code}
> Additionally, I modified the connection string by adding
> {{{}?consumer.exclusive=true{}}}, so it now looks like this:
>
> {code:java}
> wss://HOST:IP/queue/FOO?consumer.exclusive=true {code}
> However, the {{Exclusive}} attribute is still being set to {{{}false{}}}.
> What might be causing this issue?
> I tried this configuration in ActiveMQ versions 5.15.3 and 5.18.3. The client
> connects using the WebSocket protocol.
> Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
