Quick question about AI Bot WebSocket drops in JMeter

Architect & Flows
1

Quick question about the Genesys Cloud AI Bot integration. JMeter 5.6 drops connections after 100 concurrent sessions with a 1006 error. is there a specific websocket keep-alive setting i need to tweak in the jmeter thread group?

2

Check your JMeter WebSocket Sampler configuration for the ping/pong interval and the connection timeout settings.

Cause:
The 1006 error indicates an abnormal closure, often triggered when the client fails to send periodic ping frames required by the Genesys Cloud WebSocket API. Under high concurrency (100+ sessions), network latency increases, causing the server to timeout waiting for the keep-alive signal. If the JMeter thread group is not explicitly configured to handle the WebSocket control frames, the connection drops prematurely.

Solution:

  1. Enable “Ping/Pong” in the WebSocket Sampler.
  2. Set the “Ping Interval” to 15000ms (15 seconds).
  3. Ensure the “Connection Timeout” is set to at least 30000ms.
  4. Add a “WebSocket Keep Alive” sampler if using a custom plugin, or rely on the native sampler’s internal ping mechanism.

This aligns with the platform’s standard WebSocket behavior for AI Bot interactions. Verify the logs for any 408 or 401 errors if the issue persists after adjusting these parameters.