Hi @Anil Sagar
Is the Concurrent Rate Limit Policy applied only at API Proxy level or also at API Product level like we have Quota Policy ?
Also suppose I have three API Proxies AP1, AP2, AP3 pointing to same backend having concurrent rate limit as 2,3,4 respectively then how it will behave ?
Does the total of 9 (2+3+4) concurrent hits are allowed for this backend coming from any of the AP1,AP2,AP3 ?
So will it start throwing error after 2nd concurrent hit to AP1 or after 10th concurrent hit to AP1 ?
@GAURAV , Find answers below,
Is the Concurrent Rate Limit Policy applied only at API Proxy level or also at API Product level like we have Quota Policy ?
Also suppose I have three API Proxies AP1, AP2, AP3 pointing to same backend having concurrent rate limit as 2,3,4 respectively then how it will behave?
Does the total of 9 (2+3+4) concurrent hits are allowed for this backend coming from any of the AP1,AP2,AP3 ?
So will it start throwing error after 2nd concurrent hit to AP1 or after 10th concurrent hit to AP1 ?
PS: Actual allowed numbers depends on number of message processors. Trial org by default has 2 message processors. For strict counters set distributed to true & check strict on ttl. For more details refer Policy Documentation .
Hope it helps.
Hi Anil,
In your reply you have mentioned that "Actual allowed numbers depends on number of message processors" . Can you please let me know the limit per message Processor and is there any property that needs to be set ?
Thanks,
Suma