Gatling 2.3.1 websocket reconnect

We are getting status code as 1013 from the websocket server which means

/// Indicates that the service is experiencing overload. A client should
/// only connect to a different IP (when there are multiple for the target)
/// or reconnect to the same IP upon user action.
static value const try_again_later = 1013;

So,it seems,this status code is invalid and websocket is not trying to reconnect.This was added later in the RFC so may be gatling is treating it as invalid.

io.netty.handler.codec.CorruptedFrameException: Invalid close frame getStatus code: 1013
at io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder.protocolViolation(
at io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder.checkCloseFrameBody(

Is there a way we can change in the framework so that this is an accepted status code?

Please note that we are using gatling version 2.3.1 and didn’t move to 3.0.0 becuase ping/pong was not happening there.

Thanks in advance



Hi, Stefane
Is there any chance that some custom ping-pong/heartbeats will ever be supported?
E.g. STOMP protocol heartbeats:
“a[\n]” - string coming from server
“[\n]” - string sent to the server


That’s not something we plan on working on any time soon.
Contributions welcome.