load testing - Issues with websocket: Check didn't succeed by the time a new one was set up -

load testing - Issues with websocket: Check didn't succeed by the time a new one was set up -

i running performance tests using gatling. gatling scaling api calls find consistent exceptions on websockets. not sure if server-side or client-side issue. ia ms ending websocket heartbeats , waiting replies server using check(). code goes so:

... val sendheartbeat=repeat(repeatcount){ .exec( ws("send heartbeat") .sendtext("heartbeatmessage")).exithereiffailed .exec( ws("check heartbeat") .check(wslisten.within(3500).until(1))). exithereiffailed .pause(4000) } ...

the problem arises @ check stage. run tests hr or few "users" drop off giving check didn't succeed time new 1 set up error.

already answered on gatling mailing list: gatling doesn't queue messages, in case might setting check later , expect match them. maybe we'll chance that.

anyways, must set check on sendtext action, don't lose messages might arrive between sendtext , next exec.

.exec( ws("send heartbeat") .sendtext("heartbeatmessage") .check(wslisten.within(3500).until(1)))

load-testing gatling