Parameter http.requestTimeoutInMs not taken in account


I’m doing some tests on a very long request (more than 60 sec.). I tried to configurate the time out of the request in the gatling.conf file.

gatling {
http {

#maximumConnectionsTotal = -1

#maxRetry = 5
#requestCompressionLevel = -1
requestTimeoutInMs = 800000 # Timeout of the requests (ms)

Unfortunately the parameter is not used. The strange fact is that the log indicates the parameter (800000 ms in my case) but it stops after 60s.

13:44:38.017 [WARN ] c.e.e.g.h.a.GatlingAsyncHandler - Request ‘allCECHA’ failed
java.util.concurrent.TimeoutException: No response received after 800000
at com.ning.http.client.providers.netty.NettyAsyncHttpProvider$ [async-http-client-1.7.12.ja
at java.util.concurrent.Executors$ [na:1.6.0_22]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset( [na:1.6.0_22]
at java.util.concurrent.FutureTask.runAndReset( [na:1.6.0_22]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101( [na:1.6.0_22]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic( [na:1.6.0_22]
at java.util.concurrent.ScheduledThreadPoolExecutor$ [na:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( [na:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$ [na:1.6.0_22]
at [na:1.6.0_22]
13:44:38.031 [WARN ] c.e.e.g.h.a.GatlingAsyncHandlerActor - Request ‘allCECHA’ failed : No response received after 800000

Hi Gaetan,

Could try to tune the connectionTimeout parameter also ?



@Nico: IMHO, what you suggest would result in a ConnectException

@Gaetan: I suspect idleConnectionTimeout