Yes, does answer my question, thanks Vlad.
I am noticing that when the threads are spawned to achieve the target rate,
they are closed at the end of the iteration, e.g., the OMTG component starts
thread #1, #2, then finishes #1 & #2, then spawns #3, #4 etc.
This can be an issue when the threads
Hi,
I am trying to create variable throughput using throughput controller with a
variable like this
but it keeps throwing the following exception, just wonder if it's not designed
to be used like that? But using variable with a loop controller works without
any problem.
Following is how I
Pravesh wrote:
Hi Team,
I am getting one weird issue.
In jmeter when I execute the test in gui mode, in treeview listener, I can
see request details and response details what has been sent for that
request.
But when I execute the same script in non gui mode and store log file on
local, after
Does jmeter.log on your local machine show any details?
Maybe you can look at the .jtl file in an editor or (if there is no
sensitive data) post the first few lines here.
On Sun, Feb 4, 2024 at 11:52 PM Pravesh wrote:
> Hi Team,
> I am getting one weird issue.
> In jmeter when I execute the
Hi all,
Problem is resolved, it was an issue due to launching of Jmeter in a wrong
way.
Somewhere during my work, by mistake I started launching Jmeter using
ApacheJmeter executable jar in stead of Jmeter windows batch file.
Now, when I am launching Jmeter using windows batch file,
> Regarding the "Open Model Thread Group" component that was introduced in
> version 5.5, can you please explain how this component spins up threads in
> order to meet the rate requirements?
It launches threads according to the schedule.
Each thread executes its body only once.
> In particular,
