Getting j.i.IOException: Connection reset by peer in gatling when running through jenkins

Hi Can anyone help me in understanding this issue and also quick resolution to it?


usually the http debug trace log level will tell you what is wrong in the stdout file. you can enable it with 4 lines of code in your simulation file or maybe with a log4j.xml

Hi, I have tried getting the logs:

11:06:37.531 [DEBUG] o.a.n.c.NettyConnectListener - Trying to recover from failing to connect channel [id: 0xb48bd6e1, L: ! R:XXXXX.XXX:443] with a retry value of true 11:06:37.531 [DEBUG] o.a.n.c.NettyConnectListener - Failed to recover from connect exception: java.nio.channels.ClosedChannelException with channel [id: 0xb48bd6e1, L: ! R:test.XXXXX.XXXX:443] 11:06:37.531 [DEBUG] i.g.h.a.AsyncHandler - Request '' failed for user 41 java.nio.channels.ClosedChannelException: null at io.nettyr.ssl.SslHandler.channelInactive(...)(Unknown Source) Wrapped by: at at$1.onFailure( at org.asynchttpclient.netty.SimpleFutureListener.operationComplete( at io.netty.util.concurrent.DefaultPromise.notifyListener0( at io.netty.util.concurrent.DefaultPromise.notifyListeners0( at io.netty.util.concurrent.DefaultPromise.notifyListenersNow( at io.netty.util.concurrent.DefaultPromise.notifyListeners( at io.netty.util.concurrent.DefaultPromise.tryFailure( at io.netty.handler.ssl.SslHandler.notifyHandshakeFailure( at io.netty.handler.ssl.SslHandler.setHandshakeFailure( at io.netty.handler.ssl.SslHandler.channelInactive( at at at at$HeadContext.channelInactive( at at at at$AbstractUnsafe$ at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks( atty.util.concurrent.SingleThreadEventExecutor.confirmShutdown( at at io.netty.util.concurrent.SingleThreadEventExecutor$ at at

Could anyone please help me in understanding the issue here?


Connection reset by peer means the connection was closed by the server when the client was trying to send a request.
A connect exception means the server refused to open a new TCP connection.

Note that you’re using Gatling 2 which has reached end of life and is no longer maintained. Please upgrade to Gatling 3.

Thanks Stéphane for the explanation, I will upgrade the gatling to 3.

Cheers to Gatling!!!