My current config is completely failing when JMeter hits 50 concurrent WebSocket connections. The softphone disconnects immediately with 401 Unauthorized errors.
Using Genesys Cloud US1. Standard Architect flow with WebRTC media handling. JMeter 5.6 script simulates agent login and session start.
Background
Testing load capacity for agent desktop integration. Environment is Genesys Cloud US1. JMeter version 5.6. Script uses HTTP Request sampler for auth token retrieval, then WebSocket sampler for signaling. Concurrent threads ramp up to 50 over 10 seconds. Goal is to verify stability before production rollout.
Issue
At exactly 50 concurrent threads, WebSocket connections fail with 401 Unauthorized. This happens consistently. Below 40 threads, connections succeed. Error appears in JMeter log immediately after handshake attempt. No clear pattern in timing. Seems like a rate limit or session validation issue on the platform side.
Troubleshooting
- Verified API keys and scopes are correct. Single thread test works fine.
- Checked Genesys Cloud admin console for any active blocks or suspensions. None found.
- Confirmed WebSocket endpoint URL is correct for US1 region.
- Tried reducing ramp-up time to see if burst causes issue. Same result at 50 threads.
- Reviewed JMeter thread group settings. No resource exhaustion on test machine.
Has anyone seen this specific 401 behavior at this concurrency level? Is there a hidden limit on concurrent WebSocket sessions per org or per IP?