karate: Gatling report does not generate

I am running a performance test. When I use the atOnceUsers(10) injection profile there is an there is an error: There were no requests sent during the simulation, reports won’t be generated.

This causes a java error

Full error stack 17:46:10.006 [main] INFO com.intuit.karate - backend initialized 17:46:10.609 [main] INFO c.intuit.karate.netty.FeatureServer - server started - http://127.0.0.1:52131 Simulation mock.CatsKarateSimulation started… 17:46:10.897 [GatlingSystem-akka.actor.default-dispatcher-10] INFO com.intuit.karate - scenario called at line: 12 by tag: @name=delete 17:46:10.996 [GatlingSystem-akka.actor.default-dispatcher-12] INFO com.intuit.karate - scenario called at line: 12 by tag: @name=delete 17:46:11.036 [GatlingSystem-akka.actor.default-dispatcher-5] INFO com.intuit.karate - scenario called at line: 12 by tag: @name=delete 17:46:11.055 [GatlingSystem-akka.actor.default-dispatcher-13] INFO com.intuit.karate - scenario called at line: 12 by tag: @name=delete 17:46:11.073 [GatlingSystem-akka.actor.default-dispatcher-2] INFO com.intuit.karate - scenario called at line: 12 by tag: @name=delete 17:46:11.217 [GatlingSystem-akka.actor.default-dispatcher-2] INFO com.intuit.karate - scenario called at line: 12 by tag: @name=delete 17:46:11.235 [GatlingSystem-akka.actor.default-dispatcher-3] INFO com.intuit.karate - scenario called at line: 12 by tag: @name=delete 17:46:11.284 [GatlingSystem-akka.actor.default-dispatcher-9] INFO com.intuit.karate - scenario called at line: 12 by tag: @name=delete 17:46:11.288 [GatlingSystem-akka.actor.default-dispatcher-4] INFO com.intuit.karate - scenario called at line: 12 by tag: @name=delete 17:46:11.320 [GatlingSystem-akka.actor.default-dispatcher-6] INFO com.intuit.karate - scenario called at line: 12 by tag: @name=delete

================================================================================ 2019-04-04 17:46:11 0s elapsed ---- Requests ------------------------------------------------------------------

Global (OK=0 KO=0 )

---- delete -------------------------------------------------------------------- [##########################################################################]100% waiting: 0 / active: 0 / done: 10 ---- create -------------------------------------------------------------------- [##########################################################################]100% waiting: 0 / active: 0 / done: 10

Simulation mock.CatsKarateSimulation completed in 0 seconds 17:46:16.378 [GatlingSystem-akka.actor.default-dispatcher-9] ERROR com.intuit.karate - http request failed: Ask timed out on [Actor[akka://GatlingSystem/user/karate-45#-1936287571]] after [5015 ms]. Message of type [scala.concurrent.duration.FiniteDuration]. A typi cal reason for AskTimeoutException is that the recipient actor didn’t send a reply. 17:46:16.478 [GatlingSystem-akka.actor.default-dispatcher-12] ERROR com.intuit.karate - http request failed: Ask timed out on [Actor[akka://GatlingSystem/user/karate-70#-1321534357]] after [5025 ms]. Message of type [scala.concurrent.duration.FiniteDuration]. A typ ical reason for AskTimeoutException is that the recipient actor didn’t send a reply. 17:46:16.482 [GatlingSystem-akka.actor.default-dispatcher-11] ERROR com.intuit.karate - http request failed: Ask timed out on [Actor[akka://GatlingSystem/user/karate-71#1533301698]] after [5025 ms]. Message of type [scala.concurrent.duration.FiniteDuration]. A typi cal reason for AskTimeoutException is that the recipient actor didn’t send a reply. 17:46:16.808 [GatlingSystem-akka.actor.default-dispatcher-3] ERROR com.intuit.karate - http request failed: Ask timed out on [Actor[akka://GatlingSystem/user/karate-75#1263152730]] after [5025 ms]. Message of type [scala.concurrent.duration.FiniteDuration]. A typic al reason for AskTimeoutException is that the recipient actor didn’t send a reply. 17:46:16.808 [GatlingSystem-akka.actor.default-dispatcher-4] ERROR com.intuit.karate - http request failed: Ask timed out on [Actor[akka://GatlingSystem/user/karate-76#1890247501]] after [5025 ms]. Message of type [scala.concurrent.duration.FiniteDuration]. A typic al reason for AskTimeoutException is that the recipient actor didn’t send a reply. 17:46:16.809 [GatlingSystem-akka.actor.default-dispatcher-10] ERROR com.intuit.karate - http request failed: Ask timed out on [Actor[akka://GatlingSystem/user/karate-79#-870792734]] after [5025 ms]. Message of type [scala.concurrent.duration.FiniteDuration]. A typi cal reason for AskTimeoutException is that the recipient actor didn’t send a reply. 17:46:16.811 [GatlingSystem-akka.actor.default-dispatcher-2] ERROR com.intuit.karate - http request failed: Ask timed out on [Actor[akka://GatlingSystem/user/karate-80#-825752271]] after [5025 ms]. Message of type [scala.concurrent.duration.FiniteDuration]. A typic al reason for AskTimeoutException is that the recipient actor didn’t send a reply. 17:46:16.811 [GatlingSystem-akka.actor.default-dispatcher-13] ERROR com.intuit.karate - http request failed: Ask timed out on [Actor[akka://GatlingSystem/user/karate-83#-1849587794]] after [5025 ms]. Message of type [scala.concurrent.duration.FiniteDuration]. A typ ical reason for AskTimeoutException is that the recipient actor didn’t send a reply. 17:46:16.812 [GatlingSystem-akka.actor.default-dispatcher-8] ERROR com.intuit.karate - http request failed: Ask timed out on [Actor[akka://GatlingSystem/user/karate-85#1317943268]] after [5025 ms]. Message of type [scala.concurrent.duration.FiniteDuration]. A typic al reason for AskTimeoutException is that the recipient actor didn’t send a reply. Parsing log file(s)… Parsing log file(s) done Generating reports… java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at io.gatling.mojo.MainWithArgsInFile.runMain(MainWithArgsInFile.java:50) at io.gatling.mojo.MainWithArgsInFile.main(MainWithArgsInFile.java:33) Caused by: java.lang.UnsupportedOperationException: There were no requests sent during the simulation, reports won’t be generated at io.gatling.charts.report.ReportsGenerator.generateFor(ReportsGenerator.scala:49) at io.gatling.app.RunResultProcessor.generateReports(RunResultProcessor.scala:76) at io.gatling.app.RunResultProcessor.processRunResult(RunResultProcessor.scala:55) at io.gatling.app.Gatling$.start(Gatling.scala:82) at io.gatling.app.Gatling$.fromArgs(Gatling.scala:47) at io.gatling.app.Gatling$.main(Gatling.scala:39) at io.gatling.app.Gatling.main(Gatling.scala) … 6 more

karate-gatling-demo-master.zip

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 33 (15 by maintainers)

Commits related to this issue

reverting to more safer gatling pause time approach #721 this is an undo of some of the changes attempted in #564 — committed to karatelabs/karate by ptrthomas 5 years ago
ci hang issue persists, reverting change for #721 — committed to karatelabs/karate by ptrthomas 5 years ago
not doing async for steps within a scenario unit ref #721 maybe that over engineering was un-necessary, now seems to work fine for even gatling atOnceUsers the only risk is that this impacts results p... — committed to karatelabs/karate by ptrthomas 5 years ago
removing dead code from prev commit ref #721 — committed to karatelabs/karate by ptrthomas 5 years ago
handle http client exception also for gatling #721 — committed to karatelabs/karate by ptrthomas 5 years ago

Most upvoted comments

@ptrthomas , I just tested my project with the develop branch source code, and all timeout requests are now showing as “KO” which is very good, thanks a lot.

houchj on May 13, 2019

@houchj thanks, I’m pretty sure it is because we were not handling an http client exception for the gatling integration. I’ve just made a commit to the develop branch. you will need to help us by building from source and then running your test again, let us know.

ptrthomas on May 13, 2019

@ptrthomas thank you, it works nicely.

houchj on May 7, 2019

@houchj it is there https://repo1.maven.org/maven2/com/intuit/karate/karate-core/0.9.3.RC1/

try appending -U to your maven command

ptrthomas on May 6, 2019

Hi, Im the author of https://stackoverflow.com/questions/55794928/karate-gatling-one-request-is-not-recorded

Verified that AtOnceUsers, rampUsers and other gatling functions are working perfectly after the fix, all the requests are fired and recorded successfully in the report. Thanks @ptrthomas @paulmccormack @tellisnz-shift

Swiftkage on Apr 29, 2019

This looks good to me 😄

tellisnz-shift on Apr 28, 2019

@tellisnz-shift @paulmccormack I just made some changes and just maybe this will be end of all the problems - please do verify when you get a chance !

ptrthomas on Apr 28, 2019

@ptrthomas sorry i haven’t got back. I had a product launch this weekend so had to work. I am going to look into this tonight so I will update you on my findings.

paulmccormack on Apr 9, 2019