Hi,
I’m wondering what happen when the simulation reaches the maximum duration. (http://gatling.io/docs/2.1.4/general/simulation_setup.html#maximum-duration)
- If some sessions are still running when maximum duration is reached, is there a way to make a call right before the simulation finishes? (e.g. I want to make a request to log out all the users even if they are not finished)
- Is everything properly cleaned up when maximum duration is reached? Sometimes I see akka actor message (dead letters encountered) after the maxDuration is reached. I’m wondering if I can clean them up properly.
Thanks,
Brian
Hi,
I'm wondering what happen when the simulation reaches the maximum
duration. (
http://gatling.io/docs/2.1.4/general/simulation_setup.html#maximum-duration
)
1. If some sessions are still running when maximum duration is reached, is
there a way to make a call right before the simulation finishes? (e.g. I
want to make a request to log out all the users even if they are not
finished)
No
2. Is everything properly cleaned up when maximum duration is reached?
Sometimes I see akka actor message (dead letters encountered) after the
maxDuration is reached. I'm wondering if I can clean them up properly.
INFO log messages. You can ignore them, or even turn it off:
Classic Logging • Akka Documentation.
Resources (IO and ActorSystem are properly shut down).
What happen is that I have a custom feeder where it has a scala.concurrent.Channel (a FIFO queue, http://www.scala-lang.org/api/2.11.5/index.html#scala.concurrent.Channel) object. When the scenario needs a record from the feeder, it reads from the channel. And if the channel is empty, it will be blocked until something is available. However, if maximum duration is expired while the channel is blocked, Gatling “Simulation finished” is shown but the process is not killed.
Shut it down in an “after” block in the simulation.
Thank you for the suggestions, that should help. Let me looking into it.