Jmeter Loop controller is not sending all the request given in loop count

Question

I have Simple scenario:

Thread Group - One user sign in
- HTTP Sampler for Sign in
- Loop Controller - count as 10
  - HTTP Sampler for check page

As per the logic, it is working fine for 1-time sign in, 10 times check the page.

But if I give the same with 10 Users sign in, 100 times from check page, it is not sending all the requests to the server.

It is sent only around 60 to 70 request for check page. other requests are not sent from the JMeter.

Server side CPU usage getting 100%, is it restricting the JMeter to send the request further?

Is the execution completed? can you share the screenshot of ViewResultsTree? — Naveen Kumar R B
– Naveen Kumar R B, Commented Nov 10, 2016 at 10:42
Yes, Execution completed, I have disabled listeners and executing jmeter from non GUI mode. — Devarajan
– Devarajan, Commented Nov 10, 2016 at 10:48
can you please share the TestPlan screenshot? Did you check the count of samplers sent in the .jtl/.csv file? If server is crashed you could have got 500 error, but the record for each iteration should have been entered. If Load Generator machine is overloaded, it will slow down the requests to be sent, but not completely skipping them. — Naveen Kumar R B
– Naveen Kumar R B, Commented Nov 10, 2016 at 10:52
As you kept Loop Controler inside an If Controller, there are high chances that the condition might have failed, hence resulting in not executing of samplers which are inside If Controller. — Naveen Kumar R B
– Naveen Kumar R B, Commented Nov 10, 2016 at 11:08
If controller is used to check the user signed in is true. it is true only for all the users, Also if i use less no of users it is working fine with all the request. — Devarajan
– Devarajan, Commented Nov 10, 2016 at 11:10

Devarajan · Accepted Answer · 2016-11-10 13:19:17Z

2

Scheduler Enabled in Thread Group restricted the Test running time with the argument Duration.

answered Nov 10, 2016 at 13:19

Devarajan

1311 gold badge2 silver badges12 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Naveen Kumar R B · Accepted Answer · 2016-11-10 13:19:41Z

1

Scheduler Configuration set for the duration of 600 seconds causing the test to stop before all the iterations completed, which are still running.

Removing Scheduler Configuration resolved the issue and all iterations ran.

Note: The issue is identified after long discussion in the chat with the user. so question may not contain all the details.

following are some of the configuration he did in Thread Group:

Duration field: ${__P(duration,600)}
Delay : ${__P{delay,0}}

removing them resolved the issue.

answered Nov 10, 2016 at 13:19

Naveen Kumar R B

6,4385 gold badges36 silver badges68 bronze badges