WebSocket message not fully read

Hey everyone,

I’m using Gatling to load test a WebSocket API. When response messages are getting too long, they are truncated at a random position. Due to that I can’t use jsonPath for checks.

A response looks like this:


“type”: 1,
“target”: “JobStatus”,
“arguments”: [
“id”: “0fd645e9-4459-487d-86d1-9f4884203866”,
“status”: “Finished”,
“type”: “AdHoc”,
“creationDate”: “2018-12-10T15:02:40.2481534+00:00”,
“jobStarted”: null,
“workerProcessingStarted”: “2018-12-10T15:02:46.3028258+00:00”,
“lastWorkerResultReceived”: “2018-12-10T15:02:47.0925894+00:00”,
“files”: […],
“tasks”: [
“id”: “fc84c396-7f70-4513-93d3-e9fcba2b3e87”,
“jobId”: “0fd645e9-4459-487d-86d1-9f4884203866”,
“creationDate”: “2018-12-10T15:02:46.2131898+00:00”,
“actionType”: null,
“request”: {

“response”: {

“taskId”: “fc84c396-7f70-4513-93d3-e9fcba2b3e87”,
“jobId”: “0fd645e9-4459-487d-86d1-9f4884203866”,
“clientId”: “DummyClientId”,
“pipeline”: “”,


and it just gets truncated at "type and the rest is omitted.

I’m using the ASP.Net Core SignalR for the Websocket communication.

Maybe theres a problem with the delimiters. SignalR is using a \u001e to end the messages.

Kind Regards

Gatling version?

Sorry I created a second topic because I thought this one didn’t get created.

I’m using Gatling 3.0

3.0.0? 3.0.1?

There was an issue related to WebSocket fragmented frames that was fixed in 3.0.1: https://github.com/gatling/gatling/issues/3589