Trying to set up the configuration for the Digital Messaging channel for high concurrency load tests. Running JMeter 5.6 against US1 environment to validate WebSocket connection stability. The goal is to simulate 300 concurrent users initiating chat sessions simultaneously.
The initial connection phase works fine. The POST /api/v2/conversations/messages endpoint returns 200 OK. However, once the load reaches approximately 150 concurrent sessions, the WebSocket connections start dropping unexpectedly. The JMeter log shows java.net.SocketException: Connection reset for about 40% of the threads. The server side logs in Genesys Cloud show the conversations are created but then immediately transition to a closed state without any agent interaction or explicit hang-up event from the client side.
I have verified the API rate limits are not being hit, as the request volume is well below the documented limits for the tenant. The WebSocket keep-alive interval is set to default. The issue seems to be related to the server closing the socket before the message payload is fully transmitted or acknowledged.
Is there a specific configuration setting in Genesys Cloud for Digital Messaging that limits concurrent WebSocket connections, or is this a known limitation during high burst loads?