# Help configuring setUp

**URL:** <https://community.gatling.io/t/help-configuring-setup/796>\
**Category:** Gatling (Open-Source)\
**Created:** [January 29, 2014, 7:45pm UTC](https://community.gatling.io/t/help-configuring-setup/796 "2014-01-29T19:45:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmoga](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@dmoga](https://community.gatling.io/u/dmoga)\
**Post date:** [January 29, 2014, 7:45pm UTC](https://community.gatling.io/t/help-configuring-setup/796/1 "2014-01-29T19:45:39Z")

</div>

Hello all,

I’m using JMeter 2.11 but I’ve created a POC for Gatling 2 and I have to say that I’m very happy with Gatling 2.

I wanted to run the same tests from JMeter 2.11 and Gatling 2 in order to compare the results.

One example of my JMeter 2.11 config is:  
users=200  
rampup=0  
duration=3600 seconds

I’ve tried to imitate the same config from Gatling 2, something like this:

setUp(scnSetUp.inject(atOnce(1)), scnParentConsent.inject(nothingFor(5),  
rampRate(200) to (200) during (60 minutes))).protocols(httpConf)

Notes:

- I don’t need a ramp up period, I just want the same threads running for 60 minutes executing over and over the same simulation.
- I got a lot of errors from Gatling 2 and any not from Jmeter 2.11. Example: Remotely Closed [id=…] …
- setUp(scnSetUp.inject(atOnce(1)), scnParentConsent.inject(nothingFor(5), atOnce(200))).protocols(httpConf) works fine.

Question:

1. Could you tell me if the set up that I’m using is the correct one?
2. Could you tell me if there is something that I have to configure from Gatling config?

Thanks for your help.

---

<div class="post-metadata">

**Author:** ![Excilys](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@Excilys](https://community.gatling.io/u/Excilys)\
**Post date:** [January 29, 2014, 9:49pm UTC](https://community.gatling.io/t/help-configuring-setup/796/2 "2014-01-29T21:49:34Z")

</div>

Hey,

What you want to do is:

- launch 200 users at once (you know how to do that)
- wrap your scenario content into a during(3600) loop: [https://github.com/excilys/gatling/wiki/Structure-Elements#wiki-during](https://github.com/excilys/gatling/wiki/Structure-Elements#wiki-during)  
Beware that what you’re trying to do is in my sense transposing the “JMeter way”, where it’s common to reuse threads and reset their state. I just added builtins to do that in master, but in Gatling, you’d better just create new users, they are very cheap.

Cheers,

Stéphane

---

<div class="post-metadata">

**Author:** ![Excilys](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@Excilys](https://community.gatling.io/u/Excilys)\
**Post date:** [January 29, 2014, 11:12pm UTC](https://community.gatling.io/t/help-configuring-setup/796/3 "2014-01-29T23:12:33Z")

</div>

Regarding the “Remotely Closed” exceptions, that’s a problem in AsyncHttpClient I fixed and will be released this week.  
Until then, increase the maxRetry parameter in gatling.conf (something like 4). Beware of uncommenting (removing #).
