[
https://issues.apache.org/jira/browse/AMQ-9514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated AMQ-9514:
--------------------------------------
Fix Version/s: 6.3.0
(was: 6.2.0)
> 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
> Components: Transport
> Environment: ActiveMQ versions 5.15.3 and 5.18.3
> Reporter: Ondrej Mrekaj
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 6.3.0, 6.1.8
>
> Attachments: image-2025-01-08-09-35-40-171.png,
> image-2025-01-08-09-36-40-059.png, image-2025-01-08-09-37-02-833.png
>
>
> I attempted to edit the {{activemq.xml}} file as follows:
> {code:xml}
> <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:
> {noformat}
> wss://HOST:IP/queue/FOO?consumer.exclusive=true {noformat}
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
