Gatling2.0-M1. Problems with custom TimeOuts


During my test I have to set custom timeout for all requests in 180000 ms

In config file I changed:

requestTimeoutInMs = 180000 # Timeout of the requests (ms)

But all “long” requests ended with same error:

12:03:23.004 [WARN ] i.g.h.a.GatlingAsyncHandler - Request ‘payment Create new template’ failed

java.util.concurrent.TimeoutException: No response received after 180000

at com.ning.http.client.providers.netty.NettyAsyncHttpProvider$ [async-http-client-1.7.13.jar:na]

at java.util.concurrent.Executors$ Source) [na:1.6.0_45]

at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source) [na:1.6.0_45]

at java.util.concurrent.FutureTask.runAndReset(Unknown Source) [na:1.6.0_45]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source) [na:1.6.0_45]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source) [na:1.6.0_45]

at java.util.concurrent.ScheduledThreadPoolExecutor$ Source) [na:1.6.0_45]

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [na:1.6.0_45]

at java.util.concurrent.ThreadPoolExecutor$ Source) [na:1.6.0_45]

at Source) [na:1.6.0_45]

12:03:23.008 [WARN ] i.g.h.a.GatlingAsyncHandlerActor - Request ‘Budget payment Create new template’ failed : No response received after 180000

12:03:23.009 [TRACE] i.g.h.a.GatlingAsyncHandlerActor -

End test elapsed after 135 seconds, so as I understand there wasn’t requested 3 minutes timeouts for requests

Hi Natalja,

The issue was in async-http-client and I fixed them in (version 1.8.1).
Sadly, this version has some API changes that make it incompatible with previous versions.

Gatling master already targets this version, so will next milestone (2M4).
We’re basically feature complete for this new milestone and are starting testing and writing documentation.
We plan on releasing in about 2 weeks.

If you feel adventurous, you can grab a snapshot on Sonatype:



Hi, Stéphane

Thank You for such quick response!
As I wrote in another question, I try migrate to newer Gatling version. But with M3 has no luck - I have several tens working test and each of them has many errors with M3. So I try M2. Is this problem was resolved in Gatling2.0.0-M2?

Honestly, I don’t remember. You can browse the milestones content (,,

Honestly, I’ve optimized XPath A LOT in upcoming version and the code that seems to have a problem for you in M1 is no longer there.

If you want, you can anonymize your files, upload them somewhere and I can migrate them for you.