-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Description
Expected behavior
The bug #6044 has not been fixed properly and still exist.
Using a transaction controller for every thread and loop an entry will be written in the result file. Elapsed time should be the duration of this process within the transaction controller for this loop.
But when thread finishes another entry will be written for the transaction controller with the same label and elapsed time = 0. This entry is good for the logs but must not be written in the result file.
Actual behavior
For me the reason is:
If you are using a transaction controller for every thread and loop an entry will be written in the result file which is ok. When the thread finishes another entry will be written for the transaction controller with the same label and elapsed time = 0. This entry causes the min time = 0 and it messes up the statistics.
Steps to reproduce the problem
Inside a thread group (with one or more threads) use a transaction controller with one module controller inside that points to a simple controller inside a test fragment. The simple controller should have a sampler (e.g. http request sampler). Run this for a short time (e.g. 1 min) with some sampler executions. In the result file you will find entries which are labeled with the transaction controller name and the last entry is the one for the thread finished event. You can compare the time stamp in the log file for the "Thread finished" notification. And in the result file this entry has elapsed time = 0.
JMeter Version
5.6.3
Java Version
openjdk 17
OS Version
Windows 11 24H2 or linux as well