ConnectTimeoutException: connection timed out:

[Kapil]

getting loads of error when ramping more user. is this something to do with gatling configuration or server issue ?

10:39:43.720 [DEBUG] i.g.h.a.AsyncHandler - Request 'TX02_Login_SubmitLogin' failed for user 36

io.netty.channel.ConnectTimeoutException: connection timed out:  XXXXXXXXXXX/XXXXXXXX:443

        at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:218)

        ... 7 common frames omitted

Wrapped by: java.net.ConnectException: connection timed out:  XXXXXXXXXXX/XXXXXXXX:443

        at org.asynchttpclient.netty.channel.NettyConnectListener.onFailure(NettyConnectListener.java:168)

        at org.asynchttpclient.netty.request.NettyChannelConnector$1.onFailure(NettyChannelConnector.java:103)

        at org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:28)

        at org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:20)

        at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:507)

        at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:500)

        at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:479)

        at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:420)

        at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:122)

        at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:220)

        at io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38)

        at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:120)

        at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:399)

        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:464)

        at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:131)

        at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:138)

        at java.lang.Thread.run(Thread.java:748)

10:39:43.720 [WARN ] i.g.h.a.ResponseProcessor - Request 'TX02_Login_SubmitLogin' failed: j.n.ConnectException: connection timed out: XXXXXXXXXXX/XXXXXXXX:443

[Stéphane LANDELLE]

Most likely server issue.

Stéphane Landelle

GatlingCorp CEO

slan...@gatling.io

--
You received this message because you are subscribed to the Google Groups "Gatling User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gatling+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Stéphane LANDELLE]

It's all in the doc: https://gatling.io/docs/current/http/http_protocol/#connection-sharing

Stéphane Landelle

GatlingCorp CEO

slan...@gatling.io

On Mon, Mar 19, 2018 at 3:50 PM, Kapil <kapilj...@gmail.com> wrote:

I have raised this in other thread but let me ask here as well

is there anyway to reuse HTTP connections instead of creating a new HTTP connection for each test iteration / loop in Gatling tool ?

Most likely server issue.

To unsubscribe from this group and stop receiving emails from it, send an email to gatling+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.