Solace Community is getting a facelift!
On March 3rd we will be starting the process of migrating Solace Community to a new platform. As a result, Solace Community will go in to a temporary read-only state. You will still be able to come onto Solace Community and search through posts to find answers, but you won't be able to ask questions, post comments, or react in any way.
We hope to have the migration complete by Wednesday March 5th (or sooner), so please keep an eye out!
Maximum Connections per client

We are trying to replace existing activeMq with solace broker. We are trying some POC on this.
Problem: We are getting error message 503: Max Client Queue and Topic Endpoint Flow Exceeded when number consumers on the client exceeds more than 100. We also tried increasing the max connection to 500 through solace yaml file but broker does not starts and complains about this is not accepted value as shown in attatched file . Appreciate any explanation on this. Thanks
Comments
-
Hi, yes the software broker has Scaling Tiers that define hard limits on the number of connections the deployment will support. For finer-grained limits, you can scale up your broker to 1k connections but then for each virtual broker and queue set whatever lower limits you want in terms of max concurrent connections.
The Standard Edition (free version) maxes out at the 1k connections scaling tier, and requires at least 2 cores and 5.3GB vmem.
You can change the current scaling tier via the CLI or via your config-keys; there's documentation for either approach. I personally just do it at the CLI but not it'll auto-shutdown the docker container and you will need to restart that container to make the change effective. Scaling tier is one of the very few changes that requires a full restart.
0 -
Thanks for the reply. We are successfully able to increase virtual memory to 5.3 GB and able to configure around 1000 consumers.
0