Just noticed that our load tests against the BYOC Edge instance are failing consistently when we ramp up concurrency. We are trying to validate the WebSocket stability for a high-volume contact center deployment in Singapore. The setup involves JMeter 5.6.2 running from a local EC2 instance in ap-southeast-1. We are targeting the standard WebSocket endpoint for media streaming, expecting it to handle at least 500 concurrent streams based on the Edge capacity documentation.
The issue appears when we exceed roughly 150 concurrent WebSocket connections. The connections initially establish successfully, returning 101 Switching Protocols. However, within seconds, a significant portion of the connections drop with a close code of 1006 (Abnormal Closure). There is no specific error message in the WebSocket frames, just a sudden disconnect. The HTTP handshake logs show no 429s or 503s, which suggests the issue might be at the transport layer or the Edge proxy configuration rather than the Genesys Cloud API backend itself.
We have verified that the TLS certificates are valid and the time sync on the JMeter servers is accurate. The Edge instance is a standard BYOC deployment. We are using the default WebSocket keep-alive settings in JMeter. Here is the relevant snippet from the Edge documentation we are following:
“The BYOC Edge supports up to 10,000 concurrent WebSocket connections per instance. Connections should maintain a ping/pong heartbeat every 30 seconds to prevent idle timeout. Ensure that your load generator respects the connection rate limits to avoid triggering DDoS protection mechanisms.”
We are not hitting the 10,000 limit, obviously. But the 1006 errors are happening well before that. We suspect it might be related to how the Edge handles the burst of new connections. Is there a specific configuration for the Edge gateway that needs to be adjusted for high-burst scenarios? Or are we missing a parameter in the JMeter WebSocket sampler? The current throughput is dropping to near zero once the disconnects start. We need to understand if this is a hard limit on the initial connection rate or a bug in our test setup. Any insights on tuning the Edge for bursty WebSocket traffic would be appreciated.