[Bug 63755] New: Inconsistent behavior when Thread Group "forever" and "loop count" value set at the same time

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=63755

            Bug ID: 63755
           Summary: Inconsistent behavior when Thread Group "forever" and
                    "loop count" value set at the same time
           Product: JMeter
           Version: 5.1.1
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: leptitstagiaire@gmail.com
  Target Milestone: JMETER_5.2

In GUI, in the Thread Group configuration, it is not possible to check
"forever" loop count at the same time that "loop count" value is set, OK.

However, by editing the XML ".jmx" file, this is possible to define both
values. 

So assuming that I have this XML : 
<stringProp name="ThreadGroup.on_sample_error">startnextloop</stringProp>
<boolProp name="LoopController.continue_forever">true</boolProp>
<stringProp name="LoopController.loops">1</stringProp>


when I start Jmeter, everything is OK, the thread is going on indefinitely. 
BUT... as soon as I get an error, this thread became a "zombie" thread. 

It seems that the "ThreadGroup.on_sample_error=startnextloop" configuration is
based on the "LoopController.loops" configuration first, rather than on the
"LoopController.continue_forever" configuration. Moreover, under this
circumstances, the test is not able to finish alone at all : this thread is
still considered as "active" by jmeter, until a shutdown signal occurs.


I suggest to fix the "ThreadGroup.on_sample_error" behavior, in order for it to
consider the value of "LoopController.continue_forever" prior to
"LoopController.loops"

-- 
You are receiving this mail because:
You are the assignee for the bug.