# \[WARN \] i.g.h.a.AsyncHandler - Request 'Connexion' failed: Request reached time out of 60000 ms after 60016 ms **URL:** \ **Category:** Gatling (Open-Source)\ **Created:** [July 18, 2014, 8:04am UTC](https://community.gatling.io/t/warn-i-g-h-a-asynchandler-request-connexion-failed-request-reached-time-out-of-60000-ms-after-60016-ms/1187 "2014-07-18T08:04:21Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Landry\_Defo\_Kuate](https://avatars.discourse-cdn.com/v4/letter/l/c2a13f/32.png) [@Landry\_Defo\_Kuate](https://community.gatling.io/u/Landry_Defo_Kuate)\ **Post date:** [July 18, 2014, 8:04am UTC](https://community.gatling.io/t/warn-i-g-h-a-asynchandler-request-connexion-failed-request-reached-time-out-of-60000-ms-after-60016-ms/1187/1 "2014-07-18T08:04:21Z")
Hi, Can you explain me what is going on on my serveur (or on gatling) ? When i launch my simulation (1000Vu), 10% of my request failled with thoses 2 messages : 1- [WARN] i.g.h.a.AsyncHandler - Request ‘Connexion’ failed: Request reached time out of 60000 ms after 60016 ms 2 - 14:41:58.732 [WARN] i.g.h.a.AsyncHandlerActor - Encountered error while extracting extra request info java.lang.IllegalStateException: Response was not built at io.gatling.http.response.HttpResponse$$anonfun$receivedResponse$1.apply(Response.scala:59) ~[gatling-http-2.0.0-M3a.jar:na] at io.gatling.http.response.HttpResponse$$anonfun$receivedResponse$1.apply(Response.scala:59) ~[gatling-http-2.0.0-M3a.jar:na] at scala.Option.getOrElse(Option.scala:120) ~[scala-library-2.10.2.jar:na] at io.gatling.http.response.HttpResponse.receivedResponse(Response.scala:59) ~[gatling-http-2.0.0-M3a.jar:na] at io.gatling.http.response.HttpResponse.getStatusCode(Response.scala:60) ~[gatling-http-2.0.0-M3a.jar:na] at ma.awb.ebk.bel.simulations.BELSimulationParticulier$$anonfun$1.apply(BELSimulationParticulier.scala:23) ~[classes/:na] at ma.awb.ebk.bel.simulations.BELSimulationParticulier$$anonfun$1.apply(BELSimulationParticulier.scala:22) ~[classes/:na] at io.gatling.http.ahc.AsyncHandlerActor$$anonfun$1.apply(AsyncHandlerActor.scala:88) ~[gatling-http-2.0.0-M3a.jar:na] at io.gatling.http.ahc.AsyncHandlerActor$$anonfun$1.apply(AsyncHandlerActor.scala:88) ~[gatling-http-2.0.0-M3a.jar:na] at scala.Option.map(Option.scala:145) ~[scala-library-2.10.2.jar:na] at io.gatling.http.ahc.AsyncHandlerActor.logRequest(AsyncHandlerActor.scala:88) [gatling-http-2.0.0-M3a.jar:na] at io.gatling.http.ahc.AsyncHandlerActor.io$gatling$http$ahc$AsyncHandlerActor$$ko(AsyncHandlerActor.scala:122) [gatling-http-2.0.0-M3a.jar:na] at io.gatling.http.ahc.AsyncHandlerActor$$anonfun$receive$1.applyOrElse(AsyncHandlerActor.scala:56) [gatling-http-2.0.0-M3a.jar:na] at akka.actor.ActorCell.receiveMessage(ActorCell.scala:425) [akka-actor\_2.10-2.1.4.jar:na] at akka.actor.ActorCell.invoke(ActorCell.scala:386) [akka-actor\_2.10-2.1.4.jar:na] at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:230) [akka-actor\_2.10-2.1.4.jar:na] at akka.dispatch.Mailbox.run(Mailbox.scala:212) [akka-actor\_2.10-2.1.4.jar:na] at akka.dispatch.ForkJoinExecutorConfigurator$MailboxExecutionTask.exec(AbstractDispatcher.scala:506) [akka-actor\_2.10-2.1.4.jar:na] at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) [scala-library-2.10.2.jar:na] at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) [scala-library-2.10.2.jar:na] at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) [scala-library-2.10.2.jar:na] at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107) [scala-library-2.10.2.jar:na] Thank’s ---
**Author:** ![Excilys](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@Excilys](https://community.gatling.io/u/Excilys)\ **Post date:** [July 18, 2014, 8:11am UTC](https://community.gatling.io/t/warn-i-g-h-a-asynchandler-request-connexion-failed-request-reached-time-out-of-60000-ms-after-60016-ms/1187/2 "2014-07-18T08:11:11Z")
Those 10% requests failed to connect, so you didn’t even get a response. Which version do you use? Current snapshot has some methods that let you deal with missing response. ---
**Author:** ![Landry\_Defo\_Kuate](https://avatars.discourse-cdn.com/v4/letter/l/c2a13f/32.png) [@Landry\_Defo\_Kuate](https://community.gatling.io/u/Landry_Defo_Kuate)\ **Post date:** [July 18, 2014, 8:25am UTC](https://community.gatling.io/t/warn-i-g-h-a-asynchandler-request-connexion-failed-request-reached-time-out-of-60000-ms-after-60016-ms/1187/3 "2014-07-18T08:25:00Z")
Hi Stéphane, I currently using version 2.0.0.m3. I was not able to upgrade to snapshot version (we are using the maven version of galing) Do you know the root cause of thoses faillures ? I want to know if it i my Apache serveur who does not support so many connections, or if it’is Gatling who cannot open more conenctions to the server ? My Apache serveur stats seem ok. i can open more http connections to the serveur from the same gatling server from my browser. Can you give me pointeurs for diagnostic ? THank’s ---
**Author:** ![Excilys](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@Excilys](https://community.gatling.io/u/Excilys)\ **Post date:** [July 18, 2014, 8:34am UTC](https://community.gatling.io/t/warn-i-g-h-a-asynchandler-request-connexion-failed-request-reached-time-out-of-60000-ms-after-60016-ms/1187/4 "2014-07-18T08:34:08Z")
Don’t you have any information in the logs? Did you tune your OS? [https://github.com/excilys/gatling/wiki/Getting-Started#os-config](https://github.com/excilys/gatling/wiki/Getting-Started#os-config) ---
**Author:** ![Landry\_Defo\_Kuate](https://avatars.discourse-cdn.com/v4/letter/l/c2a13f/32.png) [@Landry\_Defo\_Kuate](https://community.gatling.io/u/Landry_Defo_Kuate)\ **Post date:** [July 18, 2014, 8:38am UTC](https://community.gatling.io/t/warn-i-g-h-a-asynchandler-request-connexion-failed-request-reached-time-out-of-60000-ms-after-60016-ms/1187/5 "2014-07-18T08:38:09Z")
I will encrease the `idleConnectionInPoolTimeoutInMs` and let you know if there are some good news. Thank’s