Close frame with status code 1000

[Georges Thuot]

Hi Peter,

‌

II’m trying unsuccessfully to capture the messages being generated by signalR. I’m using your WebSocket Single Read Sampler but am systematically getting the following message: Close frame with status code 1000 and close reason ‘null’.

Attached are 2 screenshots; the second is an example of the status code 1000 message I just referred to. The first image is taken from Chrome developer tools and indicates the type of messages being returned by signalR when the app is run in the browser. I know the topic came up in issue 53, unfortunately the person who brought it up seems to have fallen off the map after having asked his question.

Any assistance you could provide in helping us understand how to avoid having the connection shut down and capture an the incoming message would be greatly appreciated.

‌

‌

[Peter Doornbosch]

Hi,

SignalR is putting its own protocol on top of the websocket protocol (see https://github.com/aspnet/SignalR/blob/master/specs/HubProtocol.md). In order to have a successful conversation with your server, you / your JMeter testplan must adhere to this SignalR protocol definition and send messages the server can understand and are meaningful for the server. The fact that you’re receiving a close 1000 is probably indicating you did not succeed .

Although you can use the plugin to test SignalR flows, i cannot help you with that, because i’m not a SignalR specialist. The best advice i can give you is that you use WireShark to capture a normal session between client (browser) and server and then use that as example of how your test plan should be set up.

Hth,

Peter.

‌

[Georges Thuot]

Thanks Peter - I’ll give that a shot

[Zsolt Nemeth]

Hello,
Have you fixed your issue? And could you share a POC JMX file? We’re struggling with many issues and not even the Open Connection is successful on our end.
Thank you!