Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:
Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.
AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a 
. If my response doesn’t make sense for your topic, please react to it with a 
.
The max-bind-count setting is configured per queue on the Solace Event Broker — there is no global, Message VPN-level, or client profile-level setting that automatically applies a maximum bind count of 1 to all queues. You must set it individually on each queue.
To enforce a maximum of 1 bind on a specific exclusive queue, you configure max-bind-count 1 within the queue’s configuration context. When that limit is reached, any subsequent bind attempt by another client will be rejected with an error (503 “Max clients exceeded for queue”).
Note the important distinction for exclusive queues: even with the default max-bind-count of 1,000, only one consumer is active at a time — additional consumers bind but remain inactive until the active consumer unbinds. If you want to prevent any additional consumers from binding at all (not just from being active), setting max-bind-count 1 is the right approach.
Regarding a global/template-based approach: Queue templates exist and can set initial attribute values (including bind count thresholds for event generation) for client-created queues, but the documentation does not indicate that max-bind-count itself can be set via a queue template, Message VPN configuration, or client profile to apply universally across all queues.
For complete details on configuring max-bind-count and queue access types, see: