Getting 'Close frame with status code null and close reason 'null'' error in jmeter while executing a read request

Issue #169 new
Kartik Kanda created an issue

Hi,

I am working on an application where I first get a web socket connection followed by some writes and reads. on further steps, a new web socket connection gets opened which has the same server as the first connection but the path is different.

Script is passing till the first web socket connection. All web sockets writes and read are working fine for first web socket connection.

When second connection starts, script is able to open new connection and able to write the first request, but when getting first read, it is failing with below error in jmeter. Can you let me know any solution for this.

I have also tried using web socket advanced options for enabling multiple connections but even though getting same error

Error Message

Response code:Sampler error: unexpected frame type (close).
Response message:Received: Close frame with status code null and close reason 'null'

Output from browser

Comments (1)

  1. Peter Doornbosch repo owner

    Your server is sending an explicit close (frame). So, apparently, the server does not like what you are sending to it. I cannot help you with it, because i don’t the protocol (on top of websocket) that your client and server are talking.

    My general advise is always to install WireShark and capture a session between a normal client (browser in your case) and server and derive the test plan from that. If you did that already and your test is still failing, also record the test session and compare the two.

    I get a lot of question like this. The problem is not in the plugin, the problem is your test plan. I know it’s frustrating, but writing a good and correct test plan stateful communications is hard, that plugin cannot solve that problem.

    Hth,
    Peter

  2. Log in to comment