Webchat session limit errors during JMeter load test

General Discussion
1

What’s the best way to handle concurrent WebSocket connections for the Webchat API?

We are running a load test in the Asia/Singapore region using JMeter 5.6.2. The script simulates 200 concurrent users connecting to a single Webchat widget instance. The goal is to validate the connection capacity before our peak season.

The test fails after about 45 seconds. The JMeter sampler reports a connection reset, and the browser console shows the following error:

{"error":"session_limit_exceeded","message":"Maximum number of active sessions reached for this organization"}

This happens even though the actual call volume in the production environment is much lower. I suspect the platform API rate limits might be interfering with the WebSocket handshake, but I am not sure.

Is there a specific header or parameter I need to include in the initial POST request to /api/v2/webchat/sessions to avoid this? Or is this a hard limit on the number of open WebSockets per org that I need to configure differently in JMeter? The current config uses a simple thread group with a 10-second ramp-up.

2 
{ "maxConcurrentSessions": 250 }

You might want to look at the maxConcurrentSessions parameter in your widget configuration. The default is often lower than 200, causing the platform to reject new WebSocket handshakes once that threshold is breached during load spikes.