Websocket Single Write 'Use existing connection' with specified Path

I am testing a socket-based web application . The approach taken by our Dev team is to call an API which opens a connection via wss with a Server name and Path. The Path contains a server instance value and an access token which specifies the user connecting to application running the socket server. The typical Use Case is for multiple users to connect to the socket server via different browsers and each has the level of access afforded by their access token.

I am trying to simulate two users having this application ‘discussion’ via two socket connections to a server and using one computer to run the script to handle the interactions between the users. In JMeter I open two sockets to the server as different users (Say, Users A and B). I call two WebSocket Open Connection Samplers using the access tokens in the Path to differentiate between the two users. As long as all of the interactions are made by User A via WebSocket Single Write Sampler, everything works as expected. My issue is once User B attempts to write to its socket instance, within the first few Writes the threads start returning non-200 Response Codes and both User A and User B are disconnected by the server. At that point our application breaks and the socket server restarts itself to recover and the JMeter script fails while that is happening.

If I connect only as User A and use WebSocket Single Write Sampler to write to the socket multiple times, then connect to the server as User B and write to the socket multiple times, the script runs as expected. The issue seems to be maintaining two separate concurrent Websocket connections for two separate users on the same computer. The WebSocket Single Write Sampler allows me to ‘use existing connection’ or ‘setup new connection’. It is only by selecting ‘setup new connection’ where I can specify the Path which contains the access token for our user.

We would like to avoid creating a new socket connection each time the other User in the software ‘discussion’ must take action. It would be very nice to be able to have a third option in the Connection section ‘use existing connection with URL’ or ‘use existing connection with custom Path’ or something similar. The intent is to specify the Path on the existing connection call such that the access token embedded in the Path for the given user can be honored. Instead, when ‘user existing connection’ is selected the Path is grayed out.

Thanks for your time,

-Dennis

‌

Comments (4)