ingore the ramp down

[Viet Minh]

Hi Gatling Experts

I have a simulation scenario as follows :

.during( SOME_TIME ) { chain }

setUp(scn.inject(rampUsers(200) over (600 seconds))).protocols(httpProtocol)


If I do not want to wait for the "Ramp Down", Do you know how to do for stopping all vusers simulateously in the simulation program?

Thanks in advance

Viet Minh

[Stéphane Landelle]

http://gatling.io/docs/2.0.1/general/simulation_setup.html#maximum-duration

--
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+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Viet Minh]

Hi Stephane,

I follow your indication about the maxDuration method.

But I do not know how to use exactly the maxDuration method in the simulation.

So, I have made several attempts because I meet many failed compilations

Then I arrived in the simulation program as folows

val scn = scenario("Call SOA") 
  
      exec(
        http("Call SOA")
          .post("""""")
          .headers(headers_1)
          .body(StringBody(xmlbodyLine))
          .check(status.is(200)))
  
    setUp(scn.inject(rampUsers(160) over (160 seconds))).maxDuration(10 minutes).protocols(httpProtocol)

with these lines above, I can compile But when I try to run the simulation program,

I have thes error messages :   

[ERROR] [10/20/2014 14:51:59.725] [GatlingSystem-akka.actor.default-dispatcher-2
] [akka://GatlingSystem/user/$a] requirement failed: Scenario Call SOA is empty
java.lang.IllegalArgumentException: requirement failed: Scenario Call SOA is emp
ty
        at scala.Predef$.require(Predef.scala:233)
        at io.gatling.core.scenario.Simulation$$anonfun$scenarios$2.apply(Simula
tion.scala:40)
        at io.gatling.core.scenario.Simulation$$anonfun$scenarios$2.apply(Simula
tion.scala:40)
        at scala.collection.immutable.List.foreach(List.scala:318)
        at io.gatling.core.scenario.Simulation.scenarios(Simulation.scala:40)
        at io.gatling.core.controller.Controller$$anonfun$1.applyOrElse(Controll
er.scala:80)
        at akka.actor.Actor$class.aroundReceive(Actor.scala:465)
        at io.gatling.core.akka.BaseActor.aroundReceive(BaseActor.scala:23)
        at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516)
        at akka.actor.ActorCell.invoke(ActorCell.scala:487)
        at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238)
        at akka.dispatch.Mailbox.run(Mailbox.scala:220)
        at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(Abst
ractDispatcher.scala:393)
        at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
        at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool
.java:1339)
        at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:19
79)
        at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThre
ad.java:107)

14:51:59.749 [ERROR] i.g.c.c.Controller - Actor Controller crashed on message So
me(Run(advanced.OSB_SC1_Simulation@15b2e27,osb-sc1-simulation,,Timings(Some(10 m
inutes),None,Map())))
java.lang.IllegalArgumentException: requirement failed: Scenario Call SOA is emp
ty
        at scala.Predef$.require(Predef.scala:233) ~[scala-library.jar:na]
        at io.gatling.core.scenario.Simulation$$anonfun$scenarios$2.apply(Simula
tion.scala:40) ~[gatling-core-2.0.0.jar:2.0.0]
        at io.gatling.core.scenario.Simulation$$anonfun$scenarios$2.apply(Simula
tion.scala:40) ~[gatling-core-2.0.0.jar:2.0.0]
        at scala.collection.immutable.List.foreach(List.scala:318) ~[scala-libra
ry.jar:na]
        at io.gatling.core.scenario.Simulation.scenarios(Simulation.scala:40) ~[
gatling-core-2.0.0.jar:2.0.0]
        at io.gatling.core.controller.Controller$$anonfun$1.applyOrElse(Controll
er.scala:80) ~[gatling-core-2.0.0.jar:2.0.0]
        at akka.actor.Actor$class.aroundReceive(Actor.scala:465) ~[akka-actor_2.
10-2.3.6.jar:na]
        at io.gatling.core.akka.BaseActor.aroundReceive(BaseActor.scala:23) ~[ga
tling-core-2.0.0.jar:2.0.0]
        at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516) ~[akka-actor
_2.10-2.3.6.jar:na]
        at akka.actor.ActorCell.invoke(ActorCell.scala:487) ~[akka-actor_2.10-2.
3.6.jar:na]
        at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238) ~[akka-actor_
2.10-2.3.6.jar:na]
        at akka.dispatch.Mailbox.run(Mailbox.scala:220) ~[akka-actor_2.10-2.3.6.
jar:na]
        at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(Abst
ractDispatcher.scala:393) [akka-actor_2.10-2.3.6.jar:na]
        at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
[scala-library.jar:na]
        at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool
.java:1339) [scala-library.jar:na]
        at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:19
79) [scala-library.jar:na]
        at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThre
ad.java:107) [scala-library.jar:na]


I think I do not use accurately the maxDuration method.


Therefore, Have you any idea about the problem ?

Thanks in advance

Viet Minh

[Stéphane Landelle]

Your problem has nothing to do with duration.

You somehow managed to remove the dot between the scenario call and the next exec so the scenario is indeed empty.

[Viet Minh]

Stephane

You are right, it's a mistake of me to forget the dot between the scenario call and the next exec.

and when I put the dot, I can compile and run the simulation
but
with this configuration of my scenario

setUp(scn.inject(rampUsers(160) over (160 seconds))).maxDuration(10 minutes).protocols(httpProtocol)

it seems that the simulation program only lasts  for 160 seconds and not for 10 minutes !


Viet Minh

[Pierre DAL-PRA]

Hi Viet Minh,

maxDuration limits the maximum run time of your simulation but does not lengthen it if your injection profile means that your simulation would end before that.

maxDuration has an effect if your simulation runs longer that the maxDuration, which is not the case here.

In your case, the simplest solution is : 

• If you removed it, wrap again your simulation in a during(10 minutes)
• remove maxDuration
• Set your injection profile so that it would run for more that 10 minutes (rampUsers(160) over (12 minutes) for example)

Cheers,

Pierre

[Viet Minh]

Hi Pierre

Thanks a lot for your help

Viet Minh