[Bug 64820] New: Flow Control Action - Break current loop issues

[bu...@apache.org]

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

            Bug ID: 64820
           Summary: Flow Control Action - Break current loop issues
           Product: JMeter
           Version: 5.3
          Hardware: PC
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: nalexic@gmail.com
  Target Milestone: JMETER_5.3.1

Created attachment 37505
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=37505&action=edit
jmx file

Hello,

I noticed that Flow Control Action when Break current loop is checked has
unexpected behavior:

1. When used in Loop, While or ForEach controllers which parent is Transaction
controller, loop is properly stopped but results are doubled in Listeners. If
Generate parent sample is checked or unchecked in Transaction controller,
behavior is the same. Runtime controller might be affected too, but cannot be
reproduced because of issue under point 2.

2. When used in Runtime controller only, Break current loop actually stops
current thread. Last Dummy Sampler in TG2 is not executed.

Check provided jmx file for more info. TG1 point 1 and TG2 point 2.

Jmeter 5.3
Microsoft Windows 10 Enterprise 64-bit
java version "14.0.1" 2020-04-14

Note: There might be more issues for flow control action when Break current
loop is used, so if you have time please investigate. Thank you.

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

[Bug 64820] Flow Control Action - Break current loop issues

[bu...@apache.org]

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

Felix Schumacher <fe...@internetallee.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|critical                    |enhancement
             Status|NEW                         |NEEDINFO
                 OS|                            |All

--- Comment #1 from Felix Schumacher <fe...@internetallee.de> ---
The Runtime Controller is not a loop controller. The other controllers (Loop,
While and ForEach) are. So it looks to me like the intended behaviour.

We could
 *) add documentation, to make it clearer (where and what?)
 *) change the behaviour (possibly breaking other test plans, that use this
setup)
 *) add another flag/toggle to make the Runtime Controller behave like the
looping ones

I am unsure, which one would be best, so it is probably better to start a
discussion on the dev mailing list.

PS. please don't use third party components for minimal test plans, as it makes
it harder for us to use them and decide if it affects JMeter components only.
Instead of the Dummy Sampler I tend to use a JSR223 Sampler consisting of a
simple String (which gets returned as the body with a 200-status). (Apart from
this, I really liked the well structured test plan, that showed what you
wanted. Thanks)

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

[Bug 64820] Flow Control Action - Break current loop issues

[bu...@apache.org]

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

--- Comment #2 from eR@SeR <na...@gmail.com> ---
Hello,

Thank you for your explanation about point 2. Btw, did you see/try the issue
under point 1?

"*) add documentation, to make it clearer (where and what?)"

I agree.

"*) change the behaviour (possibly breaking other test plans, that use this
setup)"

What did you mean by this? Can you give an example maybe?

"*) add another flag/toggle to make the Runtime Controller behave like the
looping ones"

This would be really nice :) Also, I had scenarios where I wanted to finish the
execution of all child samplers inside the Runtime controller even if the timer
had expired. If you consider adding this feature, I can test it.

P.S. I didn't know that we should not provide any 3rd party components when
creating a bug report. Maybe
https://bz.apache.org/bugzilla/page.cgi?id=bug-writing.html or other rules page
should be updated to state that.

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