https://issues.apache.org/bugzilla/show_bug.cgi?id=56433

Ramon Buckland <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #3 from Ramon Buckland <[email protected]> ---
Created attachment 32351
  --> https://issues.apache.org/bugzilla/attachment.cgi?id=32351&action=edit
Updated Sample with 2 Threads

Checking that JMX, it indeed only cycles the actions of u1 and not for u2.
It is by design, although the inferred intention is that u1 and u2 both follow
actions a..d.

I changed the JMX (attached) so that there is 2 threads, and the "Actions" CSV
is bound to the "current thread". This was the "inferred" activity works.
(Sharing Mode Current Thread).

On a single thread, the Actions CSV hits EOF and is never reset. And since
there is one thread, u1 uses up all the rows.

To make it single thread (do all of u1, and then (after) all of u2) the
solution would be to loop the ACTIONS CSV with a "Reset on EOF", but you cannot
use the EOF in the while loop. (as it gets reset.. so know the number of
actions (4) and loop that or some other magic.

1    16:12:30.877    Thread Group 1-1    Login as u1    346    Success    15   
0
2    16:12:31.230    Thread Group 1-1    u1 -> Action = none    196    Success 
  0    0
3    16:12:31.432    Thread Group 1-1    u1 -> Action  a    122    Success   
12    0
4    16:12:31.399    Thread Group 1-2    Login as u2    346    Success    15   
0
5    16:12:31.559    Thread Group 1-1    u1 -> Action  b    249    Success   
12    0
6    16:12:31.750    Thread Group 1-2    u2 -> Action = none    210    Success 
  0    0
7    16:12:31.817    Thread Group 1-1    u1 -> Action  c    252    Success   
12    0
8    16:12:31.967    Thread Group 1-2    u2 -> Action  a    147    Success   
12    0
9    16:12:32.077    Thread Group 1-1    u1 -> Action  d    257    Success   
12    0
10    16:12:32.120    Thread Group 1-2    u2 -> Action  b    300    Success   
12    0
11    16:12:32.396    Thread Group 1-2    u2 -> Action  c    121    Success   
12    0
12    16:12:32.315    Thread Group 1-1    Logout    270    Success    13    0
13    16:12:32.523    Thread Group 1-2    u2 -> Action  d    244    Success   
12    0
14    16:12:32.589    Thread Group 1-1    Action = <EOF>    289    Success    0
   0
15    16:12:32.774    Thread Group 1-2    Logout    219    Success    13    0
16    16:12:32.998    Thread Group 1-2    Action = <EOF>    217    Success    0
   0

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

Reply via email to