Hi, I’m testing a websocket service, the scenario should be: Each client keeps the connection open and sends 1 message with a random unique sequence number every 10 seconds. Server returns the seq in response body. Client should only accept the message with the same seq. I also want to print the…

And here you’re comparing a long and a String, so it’s bound to fail. I found out the root cause, nothing to do with test code or gatling. There was a bug in our server code, in some circumstances, server sends msg to a wrong channel.

[image] nobody: session -> { session.markAsSucceeded(); String nanoTime = String.valueOf(System.nanoTime()); Session is immutable: Gatling - Session API .

Thank you slandelle. The 1st problem is solved, but the 2nd one still here. New code: .exec(session -> { Session newSession = session.markAsSucceeded(); String nanoTime = String.valueOf(System.nanoTime()); return newSession.set("seq", System.currentTimeMillis() + nanoTime.substring(na…

Your matchJsonPath (missing from your sample) is likely wrong. .matching( jsonPath(matchJsonPath).ofLong().isEL("#{seq}").saveAs("returnSeq") ) Note that saveAs here won’t work (in matching).

matchJsonPath is using the default value and unchanged during the test. If the jsonpath is wrong, all requests should fail. String matchJsonPath = System.getProperty("matchJsonPath", "$.body.seq"); The response body is fixed (except client seq($.body.seq), server seq($.seq) and timestamp), so $.b…

Under higher concurrency, more and more responses seemed to fail to match the “seq” attribute in Session? [image]

session.set(“seq”, System.currentTimeMillis() + nanoTime.substring(nanoTime.length() - 5)); “seq” is a String here. jsonPath(matchJsonPath).ofLong().isEL(“#{seq}”).saveAs(“returnSeq”) And here you’re comparing a long and a String, so it’s bound to fail.

[Need Help] Strange behavior of WebSocket checks

Gatling (Open-Source)

slandelle August 18, 2022, 2:51pm 10

Then, if you face an issue, please provide a reproducer as instructed here: How to Ask a Question.

Topic		Replies	Views
using session in websocket result check Gatling (Open-Source)	2	135	August 28, 2020
websocket check (wsAwait) not working, timing out even when messages are received Gatling (Open-Source)	3	426	February 16, 2018
Cannot print a response from WebSocket server Gatling (Open-Source)	0	177	November 1, 2017
Websocket API questions Gatling (Open-Source)	3	166	February 18, 2016
Latency for WS messages Gatling (Open-Source)	1	142	March 19, 2021

[Need Help] Strange behavior of WebSocket checks

Related topics