1
votes

I am using JMeter 2.11 for simulate 10000 thread users. I use CSV data set config to simulate 10000 user load and take 2-3 HTTP request in my test plan. All 10000 user load applied successfully by Jmeter but main problem is when my last request goes idle (as I put my Jmeter http request on home page of my website) all sessions goes timed out after some time. I also configure "app pool's Idle time out=0" and my application's web config's "session state timeout is 20" (I also increase this time from 20 min but no way). Also Keep Alive is checked on all http request.

Please suggest me what to do for keep my last request's session alive.

1
What code do you have currently and what have you tried so far in order to check what you're after?gabe3886

1 Answers

1
votes

JMeter threads are never idle, if thread doesn't have any more samplers to execute or no more loops to iterate it's being shut down. 10 000 users is quite a high load, it might be a problem with your JMeter configuration, i.e. it is not capable of generating and sustaining 10 000 threads. In 99% of cases jmeter.log file has enough troubleshooting information.

In the meantime few recommendations:

  1. Upgrade to the latest version of JMeter (for the moment it's Apache JMeter 2.13)
  2. Make sure you use 64-bit server JRE or JDK
  3. Provide JMeter enough Java Heap space, by default it comes with 512Mb only which is not enough to simulate 10k users
  4. Run JMeter test in non-GUI mode
  5. Disable all Listeners during test run

See 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure for above points explained and few more tips and tricks.