Why does this setting block JMeter WebSocket bursts?
Running a load test from Singapore against the platform API. We are pushing 500 concurrent WebSocket connections using the standard JMeter WebSocket sampler. The connections establish fine initially, but after 200 active sessions, the server starts returning 403 Forbidden errors on the heartbeat frames. We have verified the JWT tokens are valid and not expired. The Architect flow is simple, just routing to a queue. We are hitting a hidden concurrency limit on the WebSocket endpoint or is there a specific security policy in the org settings that throttles rapid connection attempts? The error logs show SECURITY_VIOLATION: RATE_LIMIT_EXCEEDED but this is for connections, not messages. We are using the latest JMeter WebSocket plugin and Genesys Cloud API v2. Need to know if we should adjust the X-Genesys-Client-Id headers or if there is a backend limit we are unaware of.