Unexpected frame type.,Received: Close frame with status code 1000 and close reason 'null' at open websocket connection request

[Shweta]

Hi Peter, Thanks for the plugin. This is a nice plugin and handles websocket connections well.

I know you had tested the websocket connections with 1000 concurrent connections. I am running a test where I have to test it with 400,000 concurrent connections. I am facing an issue where after around 50K connections, I start seeing a lot of close reason errors while trying to open a new connection. ERROR - eu.luminis.jmeter.wssampler.RequestResponseWebSocketSampler: Unexpected frame type received in sampler 'WebSocket Sampler-Connect to Channel': Close frame with status code 1000 and close reason 'null'

I don't see this error when i execute a test with small number of users. I understand it is a perfectly normal behavior for the closed message response to be received after the connection is closed however, it shouldn't fail opening a new connection.

My test scenario is :1Open home page 2. Open websocket connections 3. listen to channels. 4.Send Action 7 request to request the server to close connection 5. Call Websocket close sampler 6. Navigate to another page 7. open new websocket connection request 8. Connection.

Total 3 websocket connections are opened and closed per iteration by a user.

I do not see issues until approx. 50K concurrent connections. I am testing using AWS Load Generators. I have even tried adding a Text Frame filter at Websocket open request but didn't help.

[Shweta]

Development team checked if there were any issues at their end however, all the requests sent to the server were provisioned. Which makes me believe that the Web Socket Open connection sampler stopped sending requests.

[Peter Doornbosch]

Hi Shweta,

Thanks for your feedback.

Which sampler in your testplan is exactly the one that is getting the "unexpected frame type" errors?

[Shweta]

Thanks for the reply Peter. The websocket request response sampler is the one throwing the error. I get the error in non-GUI mode even with a few users as well. Strangely those errors don’t pop up in GUI mode. The sampler name is : WebSocket Sampler-Connect to Channel. Thanks Shweta

[Peter Doornbosch]

I see at least 6 request-response samplers in your test plan. Which sampler exactly is the one that is getting the "unexpected frame type" errors?

[Peter Doornbosch]

No answer? I guess you solved it?