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!

Max Client Queue and Topic Endpoint Flow

madhu
madhu Member Posts: 13 ✭
in PubSub+ Event Broker #1

Solace version: 10.2.0.26 hosted on AWS Ec2 instance.

Solace default VPN had 100 as the default setting for various connections. We have updated it to 1000 and restarted the appliance.

Used cmds below to restart the solace:

solacectl cli

enable

reload


Boomi EDi is used to connect to queue as listener. When we got the below error on boomi , we have updated the solace settings to 1000 from 100. Still we are seeing the same error any insights would be helpful.

Comments

  • madhu
    madhu Member Posts: 13 ✭
    #2
    solace_settings.PNG

    Attached solace settings and boomi error screenshots

    boomi_error.png


  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 668 admin
    #3

    Hi @madhu . That basic PubSub+Manager screen doesn't show anything about Flows. Which is what your client error is about. Please check Guaranteed messaging stats:

    image.png


    I'm not sure if the error is for the whole broker (hitting the max # of Flows), or for the Message VPN, or for the specific queue you're trying to bind to. Check the max configured bind count for the queue you're connecting to, and see how many consumers you currently have bound to it.

Categories

This Month's Leaders

This Week's Leaders