Bug 63755 - Inconsistent behavior when Thread Group "forever" and "loop count" value set at the same time
Summary: Inconsistent behavior when Thread Group "forever" and "loop count" value set ...
Status: NEW
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 5.1.1
Hardware: PC Linux
: P2 major (vote)
Target Milestone: JMETER_5.2
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-19 13:34 UTC by Nicolas
Modified: 2019-09-19 13:34 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas 2019-09-19 13:34:11 UTC
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"