Getting connection timeout in WebSocket Open Connection

[A z]

I am facing one issue for Open Connection, Thread group is configured for 10 users, out of which 5 are able to estabilish connection properly but few are not. Error message says that it's time-out issue. This issue is intermittent. Sometimes none of the user is able to establish connection whereas sometimes above 100 user is not able to establish the connection.
However, at the same time through the browser, I am able to estabilish connection properly. My host is SignalR which is hosted in .net core

I have tried to increase connection timeout to 90000 and read timeout to 60000
I have followed following block
https://medium.com/@goldberg_rui/test-signalr-performance-with-jmeter-59083554f917

Could you please have a look into this,

Thread Name: Stream 1-6
Sample Start:2022-06-22 21:45:13 IST
Load time:2000
Connect Time:0
Latency:0
Size in bytes:0
Sent bytes:0
Headers size in bytes:0
Body size in bytes:0
Sample Count:1
Error Count:1
Data type ("text"|"bin"|""):
Response code:Websocket I/O error
Response message:WebSocket I/O error: connect timed out

SampleResult fields:
ContentType:
DataEncoding: null

I am also getting 404 errors sometimes but through browser able to establish connection

Thread Name:SignalR Stream 1-6
Sample Start:2022-06-23 00:25:17 IST
Load time:1316
Connect Time:0
Latency:0
Size in bytes:0
Sent bytes:0
Headers size in bytes:0
Body size in bytes:0
Sample Count:1
Error Count:1
Data type ("text"|"bin"|""):
Response code:404
Response message:Got unexpected status 404 with statusLine:HTTP/1.1 404 Not Found

SampleResult fields:
ContentType:
DataEncoding: null

[Peter Doornbosch]

Well, it seems your test is successful in that you detected a problem / bug in your server!

A connect timeout is exactly what it says it is. There is nothing the plugin can do if your server does not respond.

A 404 means you are sending an incorrect request: the URL you are request cannot be found. This is an error in your test plan, not in the plugin. This often happens with SignalR, as people have not correctly implemented the SignalR protocol in their test plan.

Note the plugin can be used to test with SignalR, but the plugin is not a SignalR implementation in itself: you must somehow implement (simulate) the SignalR protocol in the test plan.

[A z]

The server is responding at the same time I have tried with browser, the browser is able to connect with WebSocket connection
for 404 its like for same testplan for a few requests I am getting timeout issue, for few 404 and same time few are getting connected its intermittent

[Peter Doornbosch]

You are saying: “I don’t understand why this fails!”

I’m saying: “I understand that you have problems, but i cannot relate them in anyway to possible problems in the plugin”.

A performance test is a complicated thing, because you are not only testing the server, but the complete setup, including testplan, JMeter behaviour that might be unexpected, the network between your client and server etc etc. There are a lot of things that can go wrong. I’m telling you that these specific symptoms (connection timeout, 404) indicate that the cause of the problem is not the plugin, but how it is used. I cannot help you with that apart from what I already did.

‌

[A z]

Ok thanks, I am also not able to load jmx file into blazemeter its showing validaiton file failed, could you please help me here?

[Peter Doornbosch]

No.

[A z]

Ok thanks Peter

[Peter Doornbosch]