1

I want to ask about the result when I execute JMeter using CLI mode.

When I'm trying to execute with JMeter in my computer, it's fine, but when I try to execute in CLI mode, it shows this error:

This

Until now, I still don't know what happened :(

here's the text in the log file enter image description here

this is the thread group enter image description here

and here the controller enter image description here

Antoni
  • 39
  • 6

1 Answers1

1

As the error suggests you should check jmeter.log file for any suspicious entries.

In the majority of cases StackOverFlow error occurs in JMeter when you have an issue with code/condition evaluation, i.e. check your:

If jmeter.log file doesn't tell the full story you can increase logging verbosity

Dmitri T
  • 159,985
  • 5
  • 83
  • 133
  • when i check the log, all of the error is StackOverFlow, and i dont use if controllers, for the thread i'm using Concurrency Thread Group, and the controller, i only use throughtput controller or is the error happened because i'm not using if controller or while controller? – Antoni Oct 06 '21 at 04:20
  • It looks like it's not a good idea to limit the number of executions of the samplers under the Concurrency Thread Group using Throughput Controller, you have **Thread iterations limit** which can be used instead. If you want you can report the issue via [jmeter-plugins](https://groups.google.com/g/jmeter-plugins) support forum or if you're a BlazeMeter customer - open a [support ticket](https://guide.blazemeter.com/hc/en-us/articles/207491229-How-to-Open-a-Support-Ticket-How-to-Open-a-Support-Ticket) – Dmitri T Oct 06 '21 at 05:14
  • but if i use **Thread iterations limit**, can i use the report to know how many concurrently user my server handle? – Antoni Oct 06 '21 at 08:02