503: Max Client Queue and Topic Endpoint Flow Exceeded

what is bind count in solace
solace durable topic endpoint

Sometimes I am getting the following error:

503: Max Client Queue and Topic Endpoint Flow Exceeded

What I need to configure to prevent such issue?

The number of "flows" is, roughly speaking, the number of endpoints to which you are subscribed. There are two types: ingress (for messages from your application into Solace) and egress (for messages from Solace into your application). You violated one of those limits. You can tell which by looking at the stack trace.

By default the limit on flows is 100. Before you increase this limit, ask yourself: are you really supposed to be subscribed to more than 100 queues/topics? If not, you may have a leak. Just as you wouldn't fix a memory leak by increasing memory, you shouldn't fix this leak by increasing the max flow. Are you forgetting to close your subscriptions? Are you using temporary queues? Despite their name, temporary queues last for the life of the client session unless you close them.

But if you really are supposed to be subscribed to so many endpoints, you may increase the max ingress and/or max egress. This can be done in SolAdmin by editing the Client Profile and selecting the Advanced Properties tab, or in solacectl by setting max-ingress or max-egress under configure/client-profile/message-spool (as explained here). (There is also max setting per message spool, but you are unlikely to have violated that.)

Message VPN-Level Guaranteed Messaging Configuration, At this level you can also configure durable queue and topic endpoints, and set Dead Egress flows are Guaranteed message client consumer flows, and ingress flows are solace(configure/message-spool)# max-egress-flows <value​> to Message VPNs does not exceed the event broker-wide message spool quota  503: Max Client Queue and Topic Endpoint Flow Exceeded in SPLUNK. 0. We connecting Solace queue from JMS_TA app to get queue data into Splunk. 503: Max Client

It looks like the "Max Egress Flows" setting in your client-profile has been exceeded. One egress flow will be used up for each endpoint that your application is binding to.

The "Max Egress Flows" setting can be located under the "Advanced Properties" tab, when you edit the client-profile.

Configuring Topic Endpoints, To configure the client access type for durable topic endpoints on the Solace To configure the maximum number of flows that can bind to a non-exclusive After this maximum number of delivered but unacknowledged messages is exceeded, to any other queue or topic endpoint (regardless of whether those endpoints  Appliance Response: 503 Max clients exceeded for queue MaxClientsForTEReached: 64: An attempt was made to bind to a Topic Endpoint that already has its maximum number of clients. Appliance Response: 503 Max clients exceeded for durable topic endpoint MaxClientsForDTEReached: 64: Obsolete.

We hit the same issue during our load test. With mere few hundred messages we started getting 503 error. We identified the issue was in our producer topic creation. Once we added caching to topic destination object and the issue was resolved.

503: Max Client Queue and Topic Endpoint Flow Exceeded in , 503: Max Client Queue and Topic Endpoint Flow Exceeded in SPLUNK. 0. We connecting Solace queue from JMS_TA app to get queue data  An attempt was made to bind to a Topic Endpoint (TE) that has already reached its maximum number of clients. (Cause: 503 Max Clients Exceeded For Durable Topic Endpoint)

Maximum Connections per client, Problem: We are getting error message 503: Max Client Queue and Topic Endpoint Flow Exceeded when number consumers on the client  503 Max clients exceeded for Queue static public number MAX_CLIENTS_FOR_TE = 117 An attempt was made to bind to a Guaranteed Messaging Topic Endpoint that has already reached its maximum number of clients.

SDKErrorSubcode Enumeration, Appliance Response: 503 Max clients exceeded for durable topic endpoint was made to crate a flow to a Queue or Topic Endpoint with an invalid selector. I am able to publish message on Queue but not on Topic which were associated with same queue, Please advise. – Abhi Singh Jul 5 '16 at 5:34 There is likely another queue or topic endpoint which contains this same topic subscription that is near the max quota.

solace-samples-c/solClient.h at master · SolaceSamples/solace , Queue endpoint Flow to add a dispatch callback entry only. <td width="300"> 503 Max clients exceeded for durable Topic Endpoint </td>. * </tr>. * <tr>. Then the client application can acquire a MessageProducer to establish a producer flow to publish messages, and/or acquire a MessageConsumer or TopicSubscriber to establish a consumer flow to receive messages in that transacted Session. A client can publish and/or consume up to a combined maximum of 256 messages in a single transaction.