Error: WebSocket closed abnormally (code 1006)
Looking for advice on why the Genesys Cloud WebRTC client disconnects after 30 seconds when simulating 50 concurrent users from Singapore using JMeter 5.6. The connection works fine for a single user but fails under load despite valid auth tokens.
The 1006 close code usually indicates a network interruption or server-side resource exhaustion, not an application-level rejection. When scaling WebRTC sessions, the signaling server often drops connections if the WebSocket keep-alive interval is misconfigured or if the STUN/TURN allocation times out under concurrent load.
Check your JMeter test plan for proper WebSocket frame handling. Ensure the ping/pong frames are being processed correctly. Also, verify that the Genesys Cloud tenant’s WebRTC capacity limits are not being hit.
Here is a sample JMeter WebSocket Request configuration that handles keep-alives:
{
"frame_type": "ping",
"payload": "",
"interval_ms": 15000
}
If the issue persists, check the genesyscloud_webrtc diagnostic logs in the tenant. Look for ice_candidate failures. Sometimes, the NAT traversal fails when multiple users connect simultaneously from the same IP block (like a load generator). Try using a TURN server relay in your test configuration to bypass direct P2P issues. This often stabilizes the connection under high concurrency.