You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2025/01/07 16:34:00 UTC
[jira] [Updated] (AMQ-9514) How to set exclusive consumer for ws connector?
[ 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.2.0
6.1.6
> 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.2.0, 6.1.6
>
>
> 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: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact