Where to set the maximum bind count for a client proifle via the management web portal

Solace Event Broker
1

On my VPN, I want all clients (or better yet, all clients using a particular client profile) to receive an error if a client tries to subscribe to the same queue more than once simultaneously.

In other words I want the queue access type to be Exclusive, but I don’t simply want the first bound IFlow to succeed with the others silently doing nothing. I explicitly want any subsequent attempts to connect simultaneously to the same queue to raise an error (exception) in the client code.

From what I understand, I can accomplish this by setting the “max-bind-count” to 1. I don’t want to play whack-a-mole, changing each queue after it is created. I want this to be set for any subscriber queue on the VPN.

But I can’t find “max-bind-count” (using that term, specifically), anywhere in the broker management portal.

Here are some settings that all “seem like they might be” that…

Under access control > client profiles > settings (show advanced settings) :

”Maximum Endpoints Created Per Client Username” … don’t think this is it.

”Maximum Outgoing Flows Per Client” - well, sort of this? But I want a client to have more than one flow if they subscribe to more than one topic. I just don’t want to allow multiple simultaneous connections all subscribed to one topic (ie, multiple connections by the same client username consuming a single queue at same time). So, maybe not this?

Under queues > Templates, I can create a new template and set “Maximum Consumer Count”. That seems like what I want. But then if I go over to client profiles, select my profile, and try to change this setting I can’t. It’s readonly.

image
image926×160 11 KB

OK, so then I went to the “other” management portal (I don’t really understand why there are two versions of this). And I found this screen, with this setting:

image
image863×1362 102 KB

But that seems like it’s total flows per client, not flows per client per queue. So, not this?

In that same “dialog” window there’s also this:

image
image546×121 9.74 KB

But it’s just free text. It’s not a dropdown which shows me the template I created in the “other” management portal. So I’m not sure this is correct either.

TL;DR: It is very unclear to me how I am meant to set a global “don’t allow more than one client to read from the same queue simultaneously”, and raise an error if they try setting.

2

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 :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

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:

3

So this is still the OP. No idea what is going on with the new login process, but I seem to have had to re-register, and I can’t switch accounts after logging out to try my original account again (at least - I guess - unless I go hunting for solace cookies, because presumably the solace website is checking for cookies and then automatically using the user it finds, without any option to not do that. Maybe rethink this design).

I don’t really trust the AI response, or at least it doesn’t seem all that helpful. It seems to be telling me that I can’t do what I want to do, but that seems unlikely. It says I can use a global template, but that the global template is not setting what I want to set. So… what would it be setting?