You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by jmeter tea <jm...@gmail.com> on 2017/10/30 13:41:18 UTC

Test Action with Target All Threads doesn't stop next sampler

When adding Test Action
<http://jmeter.apache.org/usermanual/component_reference.html#Test_Action> with
Stop/Stop Now action

You have Target options: All Threads/Current Thread

When choosing Current Thread in a multiple threads environment it stops and
don't continue further this Sampler

The problem is that when choosing *All Threads* Some threads execute other
sampler after than Test Action

It's very confusing, because I expect All Threads option to be more strict
than just Current Thread

In code I saw that in Current Threads it also stop current threads
context.getThread().stop();and in All Threads option it doesn't.

Is it a bug or a feature (adding grace period of stopping)?

For example Test Plan:

   - Thread Group (5 Threads)
      - Sampler1
      - Test Action Target: All Threads, Action Stop/Stop Now
      - Sampler2

Sampler 2 is execute only when Target: All Threads and not when Target:
Current Thread

Note: Also choosing Action Go to next loop iteration (Target field is
disabled) prevent Sampler2 to be executed

Re: Test Action with Target All Threads doesn't stop next sampler

Posted by Philippe Mouawad <ph...@gmail.com>.
Thanks for report.
I think it's an issue fixed now in trunk:
- https://bz.apache.org/bugzilla/show_bug.cgi?id=61698

Regards

On Mon, Oct 30, 2017 at 2:41 PM, jmeter tea <jm...@gmail.com> wrote:

> When adding Test Action
> <http://jmeter.apache.org/usermanual/component_reference.html#Test_Action>
> with
> Stop/Stop Now action
>
> You have Target options: All Threads/Current Thread
>
> When choosing Current Thread in a multiple threads environment it stops and
> don't continue further this Sampler
>
> The problem is that when choosing *All Threads* Some threads execute other
> sampler after than Test Action
>
> It's very confusing, because I expect All Threads option to be more strict
> than just Current Thread
>
> In code I saw that in Current Threads it also stop current threads
> context.getThread().stop();and in All Threads option it doesn't.
>
> Is it a bug or a feature (adding grace period of stopping)?
>
> For example Test Plan:
>
>    - Thread Group (5 Threads)
>       - Sampler1
>       - Test Action Target: All Threads, Action Stop/Stop Now
>       - Sampler2
>
> Sampler 2 is execute only when Target: All Threads and not when Target:
> Current Thread
>
> Note: Also choosing Action Go to next loop iteration (Target field is
> disabled) prevent Sampler2 to be executed
>



-- 
Cordialement.
Philippe Mouawad.