since 2.0.3 the RuntimeController stopped working correclty, in the following configuration: ThreadGroup + RuntimeController + LoopController (forever) the inner LoopController does not stop after the time specified in the containing RuntimeController. This seems to be a result of the recent change in the isDone, to me it looks that the endOfLoop should be checked there first, before the other conditions.
Some code fixes have been applied to CVS Head, which seem to fix it. The current nightly build contains the fix if you want to try it.
Can anyone specify exactly what the Runtime should do? It's current behavior, even with this change, strikes me as problematic.
Created attachment 27470 [details] Test plan that shows issue is fixed in TRUNK
I think issue is fixed since a while, but I submitted a Test case to show it is fixed. I tested on 2.4 and Trunk and it is ok Philippe Mouawad
In your test plan, Loop controller must have Loop count to Forever to reproduce this bug. I confirme with lastest JMeter (2.5) this bug is fixed. (with a same test plan, I can reproduce this with old 2.0.3, but not with 2.5) Thanks.
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1546