You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Nigel Donaldson <nd...@aconex.com> on 2015/05/13 07:57:16 UTC

Loop controller behaviour

I have the following arrangement (BeanShell samplers added solely for
debugging purposes):

 

Test Plan

...

- Test Fragment XYZ

-- CSV Data

...

-- If Controller ( condition: "${Fields_matchNr}"!="0" )

--- BeanShell Sampler #1

--- Loop Controller ( count: ${Fields_matchNr} )

---- BeanShell Sampler #2

---- Counter ( start: 1, max: ${Fields_matchNr} )

---- BeanShell Sampler #3

---- HTTP Request

---- BeanShell Sampler #4

--- BeanShell Sampler #5

...

- Thread Group

- ModuleController ( -> Test Fragment XYZ )

 

 

User data is drawn from the CSV file.  The run-time variable
Fields_matchNr , extracted earlier, has a value of 1 for the first user,
and 2 for the second user (it will have a value between 1 and 4 for other
users, but is not known until run-time).

 

 

I'm perplexed by my observation of differing behaviour of the loop
controller in two slightly different executions of the test-plan.

 

 

Concurrent execution:  if I initially specify 2 threads with 1 iteration,
the following expected outcome is observed:

 

2015/05/13 14:46:55 INFO  - jmeter.engine.StandardJMeterEngine: Running
the test! 

...

2015/05/13 14:46:55 INFO  - jmeter.gui.util.JMeterMenuBar:
setRunning(true,*local*) 

2015/05/13 14:46:55 INFO  - jmeter.engine.StandardJMeterEngine: Starting
ThreadGroup: 1 : MailNew 

2015/05/13 14:46:55 INFO  - jmeter.engine.StandardJMeterEngine: Starting 2
threads for group MailNew. 

...

2015/05/13 14:46:56 INFO  - jmeter.threads.JMeterThread: Thread started:
MailNew 1-1 

2015/05/13 14:46:56 INFO  - jmeter.services.FileServer: Stored:
./workload/MailNewUsers.dat Alias: ./workload/MailNewUsers.dat@1116508025 

...

2015/05/13 14:47:05 INFO  - jmeter.threads.JMeterThread: Thread started:
MailNew 1-2 

2015/05/13 14:47:07 WARN  - jmeter.util.BeanShellTestElement: Debug #1 :
Fields_matchNr = 1 

2015/05/13 14:47:07 WARN  - jmeter.util.BeanShellTestElement: Debug #2 :
Fields_matchNr = 1 

2015/05/13 14:47:07 WARN  - jmeter.util.BeanShellTestElement: Debug #3 :
Fields_matchNr = 1 

2015/05/13 14:47:08 WARN  - jmeter.util.BeanShellTestElement: Debug #4 :
Fields_matchNr = 1 

2015/05/13 14:47:09 WARN  - jmeter.util.BeanShellTestElement: Debug #5 :
Fields_matchNr = 1 

2015/05/13 14:47:13 INFO  - jmeter.threads.JMeterThread: Thread is done:
MailNew 1-1 

2015/05/13 14:47:13 INFO  - jmeter.threads.JMeterThread: Thread finished:
MailNew 1-1 

2015/05/13 14:47:15 WARN  - jmeter.util.BeanShellTestElement: Debug #1 :
Fields_matchNr = 2 

2015/05/13 14:47:15 WARN  - jmeter.util.BeanShellTestElement: Debug #2 :
Fields_matchNr = 2 

2015/05/13 14:47:16 WARN  - jmeter.util.BeanShellTestElement: Debug #3 :
Fields_matchNr = 2 

2015/05/13 14:47:17 WARN  - jmeter.util.BeanShellTestElement: Debug #4 :
Fields_matchNr = 2 

2015/05/13 14:47:17 WARN  - jmeter.util.BeanShellTestElement: Debug #2 :
Fields_matchNr = 2 

2015/05/13 14:47:17 WARN  - jmeter.util.BeanShellTestElement: Debug #3 :
Fields_matchNr = 2 

2015/05/13 14:47:18 WARN  - jmeter.util.BeanShellTestElement: Debug #4 :
Fields_matchNr = 2 

2015/05/13 14:47:19 WARN  - jmeter.util.BeanShellTestElement: Debug #5 :
Fields_matchNr = 2 

2015/05/13 14:47:27 INFO  - jmeter.threads.JMeterThread: Thread is done:
MailNew 1-2 

2015/05/13 14:47:27 INFO  - jmeter.threads.JMeterThread: Thread finished:
MailNew 1-2 

2015/05/13 14:47:27 INFO  - jmeter.engine.StandardJMeterEngine: Notifying
test listeners of end of test 

2015/05/13 14:47:27 INFO  - jmeter.services.FileServer: Close:
./workload/MailNewUsers.dat@1116508025 

2015/05/13 14:47:27 INFO  - jmeter.gui.util.JMeterMenuBar:
setRunning(false,*local*)

 

 

Sequential execution:  when I change that to 1 thread with 2 iterations
(with the same two users from the CSV file):

 

2015/05/13 14:48:50 INFO  - jmeter.engine.StandardJMeterEngine: Running
the test! 

...

2015/05/13 14:48:50 INFO  - jmeter.gui.util.JMeterMenuBar:
setRunning(true,*local*) 

2015/05/13 14:48:50 INFO  - jmeter.engine.StandardJMeterEngine: Starting
ThreadGroup: 1 : MailNew 

2015/05/13 14:48:50 INFO  - jmeter.engine.StandardJMeterEngine: Starting 1
threads for group MailNew. 

...

2015/05/13 14:48:50 INFO  - jmeter.threads.ThreadGroup: Starting thread
group number 1 threads 1 ramp-up 19 perThread 19000.0 delayedStart=true 

2015/05/13 14:48:50 INFO  - jmeter.threads.ThreadGroup: Started thread
group number 1 

2015/05/13 14:48:50 INFO  - jmeter.engine.StandardJMeterEngine: All thread
groups have been started 

2015/05/13 14:48:50 INFO  - jmeter.threads.JMeterThread: Thread started:
MailNew 1-1 

2015/05/13 14:48:50 INFO  - jmeter.services.FileServer: Stored:
./workload/MailNewUsers.dat Alias: ./workload/MailNewUsers.dat@1800331312 

2015/05/13 14:49:00 WARN  - jmeter.util.BeanShellTestElement: Debug #1 :
Fields_matchNr = 1 

2015/05/13 14:49:01 WARN  - jmeter.util.BeanShellTestElement: Debug #2 :
Fields_matchNr = 1 

2015/05/13 14:49:01 WARN  - jmeter.util.BeanShellTestElement: Debug #3 :
Fields_matchNr = 1 

2015/05/13 14:49:02 WARN  - jmeter.util.BeanShellTestElement: Debug #4 :
Fields_matchNr = 1 

2015/05/13 14:49:02 WARN  - jmeter.util.BeanShellTestElement: Debug #5 :
Fields_matchNr = 1 

2015/05/13 14:49:15 WARN  - jmeter.util.BeanShellTestElement: Debug #1 :
Fields_matchNr = 2 

2015/05/13 14:49:16 WARN  - jmeter.util.BeanShellTestElement: Debug #5 :
Fields_matchNr = 2 

2015/05/13 14:49:22 ERROR - jmeter.util.BeanShellInterpreter: Error
invoking bsh method: source       Sourced file: ...

...

2015/05/13 14:49:24 INFO  - jmeter.threads.JMeterThread: Thread is done:
MailNew 1-1 

2015/05/13 14:49:24 INFO  - jmeter.threads.JMeterThread: Thread finished:
MailNew 1-1 

2015/05/13 14:49:24 INFO  - jmeter.engine.StandardJMeterEngine: Notifying
test listeners of end of test 

2015/05/13 14:49:24 INFO  - jmeter.services.FileServer: Close:
./workload/MailNewUsers.dat@1800331312 

2015/05/13 14:49:24 INFO  - jmeter.gui.util.JMeterMenuBar:
setRunning(false,*local*)

 

For the second user (iteration), with the field-match being correct, there
is no execution in the loop controller.  Huh?   (As a result, an essential
variable is not set, and a subsequent beanshell pre-processor fails.)

 

 

What am I missing here?  Help appreciated.

 

 

Regards,

 

Nige


RE: Loop controller behaviour

Posted by Nigel Donaldson <nd...@aconex.com>.
I do, sebb, and copious amounts of them.   :)

> -----Original Message-----
> From: sebb [mailto:sebbaz@gmail.com]
> Sent: Tuesday, 19 May 2015 10:13 AM
> To: JMeter Users List
> Subject: Re: Loop controller behaviour
>
> On 19 May 2015 at 00:35, Nigel Donaldson <nd...@aconex.com>
> wrote:
> > Hello Flavio, and thanks for responding.
> >
> > In a number of cases, I use a short list of arguments to BeanShell 
> > scripts.
> > However, some of my scripts have to work with many tens of (extracted
> > run-time) variables, so a long tail of variables passed-in as
> > arguments is (IMO, impracticably) unwieldy.
>
> In that case, if you want run-time evaluation of the variable, use code 
> like
>
> vars.get("VAR1")
>
> rather than
>
> ${VAR1}
>
>
> > Nige
> >
> >
> >> -----Original Message-----
> >> From: Flavio Cysne [mailto:flaviocysne@gmail.com]
> >> Sent: Monday, 18 May 2015 10:31 PM
> >> To: JMeter Users List
> >> Subject: Re: Loop controller behaviour
> >>
> >> I didn't see before that there is an error message referring to a
> >> BeanShell sampler in JMeter's log sent in the first message. If you
> >> are using expressions like this "field_${Fields_g1}" inside your
> >> BeanShell code, I advise you to pass variables, or expressions using
> >> variables,  as arguments (i.e. don't use JMeter variables or
> >> functions inside BeanShell code, or prefer not to) to avoid
> >> interpreter exception during execution. BeanShell code is compiled to
> >> a "static" version (if "Reset before each call" is not checked).
> >>
> >> I built a script similar to which you presented, but ATM I'm not
> >> seeing errors or unexpected behaviors. I'll try to post it and send
> >> the link into this thread.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > For additional commands, e-mail: user-help@jmeter.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org


Re: Loop controller behaviour

Posted by sebb <se...@gmail.com>.
On 19 May 2015 at 00:35, Nigel Donaldson <nd...@aconex.com> wrote:
> Hello Flavio, and thanks for responding.
>
> In a number of cases, I use a short list of arguments to BeanShell scripts.
> However, some of my scripts have to work with many tens of (extracted
> run-time) variables, so a long tail of variables passed-in as arguments is
> (IMO, impracticably) unwieldy.

In that case, if you want run-time evaluation of the variable, use code like

vars.get("VAR1")

rather than

${VAR1}


> Nige
>
>
>> -----Original Message-----
>> From: Flavio Cysne [mailto:flaviocysne@gmail.com]
>> Sent: Monday, 18 May 2015 10:31 PM
>> To: JMeter Users List
>> Subject: Re: Loop controller behaviour
>>
>> I didn't see before that there is an error message referring to a
>> BeanShell
>> sampler in JMeter's log sent in the first message. If you are using
>> expressions
>> like this "field_${Fields_g1}" inside your BeanShell code, I advise you to
>> pass
>> variables, or expressions using variables,  as arguments (i.e. don't use
>> JMeter
>> variables or functions inside BeanShell code, or prefer not to) to avoid
>> interpreter exception during execution. BeanShell code is compiled to a
>> "static" version (if "Reset before each call" is not checked).
>>
>> I built a script similar to which you presented, but ATM I'm not seeing
>> errors
>> or unexpected behaviors. I'll try to post it and send the link into this
>> thread.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org


RE: Loop controller behaviour

Posted by Nigel Donaldson <nd...@aconex.com>.
Hello Flavio, and thanks for responding.

In a number of cases, I use a short list of arguments to BeanShell scripts. 
However, some of my scripts have to work with many tens of (extracted 
run-time) variables, so a long tail of variables passed-in as arguments is 
(IMO, impracticably) unwieldy.

Nige


> -----Original Message-----
> From: Flavio Cysne [mailto:flaviocysne@gmail.com]
> Sent: Monday, 18 May 2015 10:31 PM
> To: JMeter Users List
> Subject: Re: Loop controller behaviour
>
> I didn't see before that there is an error message referring to a 
> BeanShell
> sampler in JMeter's log sent in the first message. If you are using 
> expressions
> like this "field_${Fields_g1}" inside your BeanShell code, I advise you to 
> pass
> variables, or expressions using variables,  as arguments (i.e. don't use 
> JMeter
> variables or functions inside BeanShell code, or prefer not to) to avoid
> interpreter exception during execution. BeanShell code is compiled to a
> "static" version (if "Reset before each call" is not checked).
>
> I built a script similar to which you presented, but ATM I'm not seeing 
> errors
> or unexpected behaviors. I'll try to post it and send the link into this 
> thread.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org


Re: Loop controller behaviour

Posted by Flavio Cysne <fl...@gmail.com>.
I didn't see before that there is an error message referring to a BeanShell
sampler in JMeter's log sent in the first message. If you are using
expressions like this "field_${Fields_g1}" inside your BeanShell code, I
advise you to pass variables, or expressions using variables,  as arguments
(i.e. don't use JMeter variables or functions inside BeanShell code, or
prefer not to) to avoid interpreter exception during execution. BeanShell
code is compiled to a "static" version (if "Reset before each call" is not
checked).

I built a script similar to which you presented, but ATM I'm not seeing
errors or unexpected behaviors. I'll try to post it and send the link into
this thread.

Re: Loop controller behaviour

Posted by Pravesh Prajapati <pr...@gmail.com>.
Hi Mahesh,

Following are the steps which I recieved from the link which you have
provided.
remote jmeter load testing : jmeter setup for aggregate results
 We can aggregate multiple jmeter report for same test plan on single
jmeter with below steps. For that we need jmeter-server to be started.

Jemter-server1 (to execute test plan)
<Server-host1>:  /var/tmp/Jmetertest/jmeter/bin/jmeter-server
*${DIRNAME}/jmeter ${RMI_HOST_DEF} -Dserver_port=${SERVER_PORT:-1099} -s -j
jmeter-server.log "$@"*

Jmeter-server2 (to execute test plan)
<Server-host2>:  /var/tmp/Jmetertest/jmeter/bin/jmeter-server
*${DIRNAME}/jmeter ${RMI_HOST_DEF} -Dserver_port=${SERVER_PORT:-1099} -s -j
jmeter-server.log "$@"*

Jmeter-client (To aggregate results from both jmeter) – Start load test
from client
<Client-host1>:  /var/tmp/Jmetertest/jmeter/bin/jmeter.properties
remote_hosts=x.x.x.x:1099,y.y.y.y:1099


- To start load from all remote  client Go to Run > Remote Start All Client


What I had done,
I started Jmeter server on both slave machine & Added there IP's into
jmeter.properties file.

but I am not getting the above highlighted steps  what does it tries to say.
And how can we configure it.

Please reply,
Thanks in advance.
Regards,
Pravesh Prajapati.

On Tue, May 19, 2015 at 8:08 PM, Pravesh Prajapati <
prajapati.pravesh@gmail.com> wrote:

> Hi Mahesh,
> Can we do that using GUI mode.
> Say for example I have one master & I have added Aggregate report listener
> to it with the script.
> Now I am Distributing the loads on slave machine eg:-slave1=500 VU &
> slave2:-200 VU.
> Then can I get Consolidated reports from these two slaves on the Master
> machines listener.
> Please reply.
> Thanks in Advance.
> Please call on the mob no 9702600170, OR give a miss call I will cal you.
>
>
> Regards,
> Pravesh
>
>
> On Tue, May 19, 2015 at 7:25 PM, mahesh bhasme <mb...@gmail.com> wrote:
>
>> Hi Pravesh,
>>
>> You can use aggregate report to collect result from slaves. Following
>> reference ulr has steps to configure master/slave jmeter.
>>
>> http://myloadtesting.blogspot.in/2014/11/jmeter-setup-for-aggregate-results.html
>>
>>
>> Thanks,
>> Mahesh
>> http://myloadtesting.blogspot.in/
>>
>> On Tue, May 19, 2015 at 6:19 PM, Pravesh Prajapati <
>> prajapati.pravesh@gmail.com> wrote:
>>
>> > Hi Sir,
>> >
>> > Can you please provide me solution regarding to master slave
>> architecture.
>> >
>> > Say for eg:-
>> >
>> > I have one master machine & three slave machine.
>> >
>> > I have distributed load on these three slave machines are as follows.
>> >
>> > 1000 vu on slave first, 2000 vu on slave 2nd & 2500 vu on slave 3rd.
>> >
>> > Now can I have a consolidate report for 5500 VU  form Master machine.
>> >
>> > OR Is there is any mechanism from where we can consolidate the report
>> for
>> > these distributed users into Jmeter.
>> >
>> > Sir, one more question.
>> >
>> > What is the minimum hardware configuration required for running 1000 vu
>> on
>> > Slave machine.
>> >
>> >
>> > Please reply.
>> > Thanks in Advance.
>> >
>> > On Tue, May 19, 2015 at 6:31 AM, Nigel Donaldson <ndonaldson@aconex.com
>> >
>> > wrote:
>> >
>> > > I appreciate your effort, Flavio.
>> > >
>> > > I also created a new minimal Test Plan yesterday, using the same
>> JMeter
>> > > logic/elements I'd flagged, but using different, fixed values for the
>> > > 'Fields' variable (still coming from a CSV source).  It exhibited
>> similar
>> > > behaviour to what was happening in my 'real' Test Plan: the Loop
>> > Controller
>> > > was never working beyond the first iteration in any Thread Group.
>> > >
>> > > Cutting my losses, I reworked the Test Plan by replacing the If /
>> Loop /
>> > > Counter trinity with a BeanShell Sampler / ForEach Controller duo.
>> > >
>> > > Functionality is now what I expect, in that _all_ iterations in _all_
>> > > Thread
>> > > Groups now correctly 'loop over' their respective number of fields.
>> > >
>> > > Nige
>> > >
>> > >
>> > > > -----Original Message-----
>> > > > From: Flavio Cysne [mailto:flaviocysne@gmail.com]
>> > > > Sent: Monday, 18 May 2015 11:11 PM
>> > > > To: JMeter Users List
>> > > > Subject: RE: Loop controller behaviour
>> > > >
>> > > > Nigel,
>> > > >
>> > > >     I published a script in pastebin,
>> > > > http://pastebin.com/download.php?i=bL7kwXjA, using a Thread Group
>> with
>> > > > the logic you mentioned and another Thread Group using a Test
>> Fragment
>> > as
>> > > > well.
>> > > > ATM it is not using a CSV dataset nor the dynamic values per user,
>> as
>> > you
>> > > > said.
>> > > >
>> > > > Hope it helps.
>> > > > Em 18/05/2015 00:39, "Nigel Donaldson" <nd...@aconex.com>
>> > > > escreveu:
>> > > >
>> > > > > Hello, Flavio.
>> > > > >
>> > > > > I have to admit I didn't comprehend your statement per se, given
>> that
>> > > > > my CSV
>> > > > > entries _are_ being used correctly.   However, it eventually lead
>> me
>> > to
>> > > > > revisit the documentation for Loop Controller, and I've just
>> realised
>> > > > > that
>> > > > > it doesn't function how I understood it would.   (Why only once
>> per
>> > > > > thread-group?!)
>> > > > >
>> > > > > I need to reassess my approach :  a BeanShell Sampler producing
>> > > > > something for a ForEach Controller looks likely.
>> > > > >
>> > > > > Thanks again.
>> > > > >
>> > > > > Nige
>> > > > >
>> > > > > -----Original Message-----
>> > > > > From: Flavio Cysne [mailto:flaviocysne@gmail.com]
>> > > > > Sent: Friday, 15 May 2015 8:31 PM
>> > > > > To: JMeter Users List
>> > > > > Subject: Re: Loop controller behaviour
>> > > > >
>> > > > > Nice,
>> > > > >
>> > > > >     I forgot to mention that CSV Dataset config don't go to the
>> next
>> > > > > line when using loop controller. In your case, just when using
>> Test
>> > > > > Plan's Loop count.
>> > > > >
>> > > > > Hope it helps.
>> > > > >
>> > > > >
>> ---------------------------------------------------------------------
>> > > > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
>> > > > > For additional commands, e-mail: user-help@jmeter.apache.org
>> > > > >
>> > > > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
>> > > For additional commands, e-mail: user-help@jmeter.apache.org
>> > >
>> > >
>> >
>> >
>> > --
>> > Regards,
>> > Pravesh prajapati.
>> > Mob:-9702600170
>> >
>>
>>
>>
>> --
>> Thanks,
>> MAhesh
>>
>
>
>
> --
> Regards,
> Pravesh prajapati.
> Mob:-9702600170
>



-- 
Regards,
Pravesh prajapati.
Mob:-9702600170

Re: Loop controller behaviour

Posted by Pravesh Prajapati <pr...@gmail.com>.
Sure sir
I have posted by mistakenly.

On Wednesday, May 20, 2015, Nigel Donaldson <nd...@aconex.com> wrote:

> Hello Pravesh.
>
> Please create a new thread - your matter has nothing to do with the
> behaviour of a Loop Controller.
>
> Nige
>
> -----Original Message-----
> From: Pravesh Prajapati [mailto:prajapati.pravesh@gmail.com <javascript:;>
> ]
> Sent: Wednesday, 20 May 2015 2:45 PM
> To: JMeter Users List
> Subject: Re: Loop controller behaviour
>
> Hi mahesh,
> I is it compulsory to to keep the jmx file on the slave machine.
> What is did is I started jmeter server on both slave and added the ip's of
> slave mc into jmeter.properties file on master mc.
> now I executed the script from master on both slave.
>
> but I didn't any thing on slave mc.
> if I need to keep jmx file on slave so where should I keep it.
>
> can you please let me know where logs are generated on salve and master mc
> so that I can just analyse that.
>
> please reply.
>
> Thanks in advance.
>
>
> On Wednesday, May 20, 2015, mahesh bhasme <mbhasme@gmail.com
> <javascript:;>> wrote:
>
> > Yes..you can use GUI mode and get aggregate report. just keep jmx file
> > on both slave at same location and follow steps from given link
> >
> > Thanks,
> > Mahesh
> >
> > On Tue, May 19, 2015 at 8:08 PM, Pravesh Prajapati <
> > prajapati.pravesh@gmail.com <javascript:;> <javascript:;>> wrote:
> >
> > > Hi Mahesh,
> > > Can we do that using GUI mode.
> > > Say for example I have one master & I have added Aggregate report
> > listener
> > > to it with the script.
> > > Now I am Distributing the loads on slave machine eg:-slave1=500 VU &
> > > slave2:-200 VU.
> > > Then can I get Consolidated reports from these two slaves on the
> > > Master machines listener.
> > > Please reply.
> > > Thanks in Advance.
> > > Please call on the mob no 9702600170, OR give a miss call I will cal
> > > you.
> > >
> > >
> > > Regards,
> > > Pravesh
> > >
> > >
> > > On Tue, May 19, 2015 at 7:25 PM, mahesh bhasme <mbhasme@gmail.com
> <javascript:;>
> > <javascript:;>> wrote:
> > >
> > > > Hi Pravesh,
> > > >
> > > > You can use aggregate report to collect result from slaves.
> > > > Following reference ulr has steps to configure master/slave jmeter.
> > > >
> > > >
> > >
> > http://myloadtesting.blogspot.in/2014/11/jmeter-setup-for-aggregate-re
> > sults.html
> > > >
> > > >
> > > > Thanks,
> > > > Mahesh
> > > > http://myloadtesting.blogspot.in/
> > > >
> > > > On Tue, May 19, 2015 at 6:19 PM, Pravesh Prajapati <
> > > > prajapati.pravesh@gmail.com <javascript:;> <javascript:;>> wrote:
> > > >
> > > > > Hi Sir,
> > > > >
> > > > > Can you please provide me solution regarding to master slave
> > > > architecture.
> > > > >
> > > > > Say for eg:-
> > > > >
> > > > > I have one master machine & three slave machine.
> > > > >
> > > > > I have distributed load on these three slave machines are as
> > > > > follows.
> > > > >
> > > > > 1000 vu on slave first, 2000 vu on slave 2nd & 2500 vu on slave
> 3rd.
> > > > >
> > > > > Now can I have a consolidate report for 5500 VU  form Master
> > > > > machine.
> > > > >
> > > > > OR Is there is any mechanism from where we can consolidate the
> > > > > report
> > > for
> > > > > these distributed users into Jmeter.
> > > > >
> > > > > Sir, one more question.
> > > > >
> > > > > What is the minimum hardware configuration required for running
> > > > > 1000
> > vu
> > > > on
> > > > > Slave machine.
> > > > >
> > > > >
> > > > > Please reply.
> > > > > Thanks in Advance.
> > > > >
> > > > > On Tue, May 19, 2015 at 6:31 AM, Nigel Donaldson <
> > > ndonaldson@aconex.com <javascript:;> <javascript:;>>
> > > > > wrote:
> > > > >
> > > > > > I appreciate your effort, Flavio.
> > > > > >
> > > > > > I also created a new minimal Test Plan yesterday, using the
> > > > > > same
> > > JMeter
> > > > > > logic/elements I'd flagged, but using different, fixed values
> > > > > > for
> > the
> > > > > > 'Fields' variable (still coming from a CSV source).  It
> > > > > > exhibited
> > > > similar
> > > > > > behaviour to what was happening in my 'real' Test Plan: the
> > > > > > Loop
> > > > > Controller
> > > > > > was never working beyond the first iteration in any Thread Group.
> > > > > >
> > > > > > Cutting my losses, I reworked the Test Plan by replacing the
> > > > > > If /
> > > Loop
> > > > /
> > > > > > Counter trinity with a BeanShell Sampler / ForEach Controller
> duo.
> > > > > >
> > > > > > Functionality is now what I expect, in that _all_ iterations
> > > > > > in
> > _all_
> > > > > > Thread
> > > > > > Groups now correctly 'loop over' their respective number of
> > > > > > fields.
> > > > > >
> > > > > > Nige
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Flavio Cysne [mailto:flaviocysne@gmail.com
> <javascript:;>
> > > > > > > <javascript:;>]
> > > > > > > Sent: Monday, 18 May 2015 11:11 PM
> > > > > > > To: JMeter Users List
> > > > > > > Subject: RE: Loop controller behaviour
> > > > > > >
> > > > > > > Nigel,
> > > > > > >
> > > > > > >     I published a script in pastebin,
> > > > > > > http://pastebin.com/download.php?i=bL7kwXjA, using a Thread
> > Group
> > > > with
> > > > > > > the logic you mentioned and another Thread Group using a
> > > > > > > Test
> > > > Fragment
> > > > > as
> > > > > > > well.
> > > > > > > ATM it is not using a CSV dataset nor the dynamic values per
> > user,
> > > as
> > > > > you
> > > > > > > said.
> > > > > > >
> > > > > > > Hope it helps.
> > > > > > > Em 18/05/2015 00:39, "Nigel Donaldson"
> > > > > > > <ndonaldson@aconex.com <javascript:;>
> > <javascript:;>>
> > > > > > > escreveu:
> > > > > > >
> > > > > > > > Hello, Flavio.
> > > > > > > >
> > > > > > > > I have to admit I didn't comprehend your statement per se,
> > given
> > > > that
> > > > > > > > my CSV
> > > > > > > > entries _are_ being used correctly.   However, it eventually
> > lead
> > > > me
> > > > > to
> > > > > > > > revisit the documentation for Loop Controller, and I've
> > > > > > > > just
> > > > realised
> > > > > > > > that
> > > > > > > > it doesn't function how I understood it would.   (Why only
> > > > > > > > once
> > > per
> > > > > > > > thread-group?!)
> > > > > > > >
> > > > > > > > I need to reassess my approach :  a BeanShell Sampler
> > > > > > > > producing something for a ForEach Controller looks likely.
> > > > > > > >
> > > > > > > > Thanks again.
> > > > > > > >
> > > > > > > > Nige
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Flavio Cysne [mailto:flaviocysne@gmail.com
> <javascript:;>
> > <javascript:;>]
> > > > > > > > Sent: Friday, 15 May 2015 8:31 PM
> > > > > > > > To: JMeter Users List
> > > > > > > > Subject: Re: Loop controller behaviour
> > > > > > > >
> > > > > > > > Nice,
> > > > > > > >
> > > > > > > >     I forgot to mention that CSV Dataset config don't go
> > > > > > > > to the
> > > > next
> > > > > > > > line when using loop controller. In your case, just when
> > > > > > > > using
> > > Test
> > > > > > > > Plan's Loop count.
> > > > > > > >
> > > > > > > > Hope it helps.
> > > > > > > >
> > > > > > > >
> > > > ------------------------------------------------------------------
> > > > ---
> > > > > > > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> <javascript:;>
> > <javascript:;>
> > > > > > > > For additional commands, e-mail:
> > > > > > > > user-help@jmeter.apache.org <javascript:;>
> > <javascript:;>
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> <javascript:;>
> > <javascript:;>
> > > > > > For additional commands, e-mail: user-help@jmeter.apache.org
> <javascript:;>
> > <javascript:;>
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Regards,
> > > > > Pravesh prajapati.
> > > > > Mob:-9702600170
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Thanks,
> > > > MAhesh
> > > >
> > >
> > >
> > >
> > > --
> > > Regards,
> > > Pravesh prajapati.
> > > Mob:-9702600170
> > >
> >
> >
> >
> > --
> > Thanks,
> > MAhesh
> >
>
>
> --
> Regards,
> Pravesh prajapati.
> Mob:-9702600170
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org <javascript:;>
> For additional commands, e-mail: user-help@jmeter.apache.org
> <javascript:;>
>
>

-- 
Regards,
Pravesh prajapati.
Mob:-9702600170

RE: Loop controller behaviour

Posted by Nigel Donaldson <nd...@aconex.com>.
Hello Pravesh.

Please create a new thread - your matter has nothing to do with the 
behaviour of a Loop Controller.

Nige

-----Original Message-----
From: Pravesh Prajapati [mailto:prajapati.pravesh@gmail.com]
Sent: Wednesday, 20 May 2015 2:45 PM
To: JMeter Users List
Subject: Re: Loop controller behaviour

Hi mahesh,
I is it compulsory to to keep the jmx file on the slave machine.
What is did is I started jmeter server on both slave and added the ip's of 
slave mc into jmeter.properties file on master mc.
now I executed the script from master on both slave.

but I didn't any thing on slave mc.
if I need to keep jmx file on slave so where should I keep it.

can you please let me know where logs are generated on salve and master mc 
so that I can just analyse that.

please reply.

Thanks in advance.


On Wednesday, May 20, 2015, mahesh bhasme <mb...@gmail.com> wrote:

> Yes..you can use GUI mode and get aggregate report. just keep jmx file
> on both slave at same location and follow steps from given link
>
> Thanks,
> Mahesh
>
> On Tue, May 19, 2015 at 8:08 PM, Pravesh Prajapati <
> prajapati.pravesh@gmail.com <javascript:;>> wrote:
>
> > Hi Mahesh,
> > Can we do that using GUI mode.
> > Say for example I have one master & I have added Aggregate report
> listener
> > to it with the script.
> > Now I am Distributing the loads on slave machine eg:-slave1=500 VU &
> > slave2:-200 VU.
> > Then can I get Consolidated reports from these two slaves on the
> > Master machines listener.
> > Please reply.
> > Thanks in Advance.
> > Please call on the mob no 9702600170, OR give a miss call I will cal 
> > you.
> >
> >
> > Regards,
> > Pravesh
> >
> >
> > On Tue, May 19, 2015 at 7:25 PM, mahesh bhasme <mbhasme@gmail.com
> <javascript:;>> wrote:
> >
> > > Hi Pravesh,
> > >
> > > You can use aggregate report to collect result from slaves.
> > > Following reference ulr has steps to configure master/slave jmeter.
> > >
> > >
> >
> http://myloadtesting.blogspot.in/2014/11/jmeter-setup-for-aggregate-re
> sults.html
> > >
> > >
> > > Thanks,
> > > Mahesh
> > > http://myloadtesting.blogspot.in/
> > >
> > > On Tue, May 19, 2015 at 6:19 PM, Pravesh Prajapati <
> > > prajapati.pravesh@gmail.com <javascript:;>> wrote:
> > >
> > > > Hi Sir,
> > > >
> > > > Can you please provide me solution regarding to master slave
> > > architecture.
> > > >
> > > > Say for eg:-
> > > >
> > > > I have one master machine & three slave machine.
> > > >
> > > > I have distributed load on these three slave machines are as 
> > > > follows.
> > > >
> > > > 1000 vu on slave first, 2000 vu on slave 2nd & 2500 vu on slave 3rd.
> > > >
> > > > Now can I have a consolidate report for 5500 VU  form Master 
> > > > machine.
> > > >
> > > > OR Is there is any mechanism from where we can consolidate the
> > > > report
> > for
> > > > these distributed users into Jmeter.
> > > >
> > > > Sir, one more question.
> > > >
> > > > What is the minimum hardware configuration required for running
> > > > 1000
> vu
> > > on
> > > > Slave machine.
> > > >
> > > >
> > > > Please reply.
> > > > Thanks in Advance.
> > > >
> > > > On Tue, May 19, 2015 at 6:31 AM, Nigel Donaldson <
> > ndonaldson@aconex.com <javascript:;>>
> > > > wrote:
> > > >
> > > > > I appreciate your effort, Flavio.
> > > > >
> > > > > I also created a new minimal Test Plan yesterday, using the
> > > > > same
> > JMeter
> > > > > logic/elements I'd flagged, but using different, fixed values
> > > > > for
> the
> > > > > 'Fields' variable (still coming from a CSV source).  It
> > > > > exhibited
> > > similar
> > > > > behaviour to what was happening in my 'real' Test Plan: the
> > > > > Loop
> > > > Controller
> > > > > was never working beyond the first iteration in any Thread Group.
> > > > >
> > > > > Cutting my losses, I reworked the Test Plan by replacing the
> > > > > If /
> > Loop
> > > /
> > > > > Counter trinity with a BeanShell Sampler / ForEach Controller duo.
> > > > >
> > > > > Functionality is now what I expect, in that _all_ iterations
> > > > > in
> _all_
> > > > > Thread
> > > > > Groups now correctly 'loop over' their respective number of 
> > > > > fields.
> > > > >
> > > > > Nige
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Flavio Cysne [mailto:flaviocysne@gmail.com
> > > > > > <javascript:;>]
> > > > > > Sent: Monday, 18 May 2015 11:11 PM
> > > > > > To: JMeter Users List
> > > > > > Subject: RE: Loop controller behaviour
> > > > > >
> > > > > > Nigel,
> > > > > >
> > > > > >     I published a script in pastebin,
> > > > > > http://pastebin.com/download.php?i=bL7kwXjA, using a Thread
> Group
> > > with
> > > > > > the logic you mentioned and another Thread Group using a
> > > > > > Test
> > > Fragment
> > > > as
> > > > > > well.
> > > > > > ATM it is not using a CSV dataset nor the dynamic values per
> user,
> > as
> > > > you
> > > > > > said.
> > > > > >
> > > > > > Hope it helps.
> > > > > > Em 18/05/2015 00:39, "Nigel Donaldson"
> > > > > > <ndonaldson@aconex.com
> <javascript:;>>
> > > > > > escreveu:
> > > > > >
> > > > > > > Hello, Flavio.
> > > > > > >
> > > > > > > I have to admit I didn't comprehend your statement per se,
> given
> > > that
> > > > > > > my CSV
> > > > > > > entries _are_ being used correctly.   However, it eventually
> lead
> > > me
> > > > to
> > > > > > > revisit the documentation for Loop Controller, and I've
> > > > > > > just
> > > realised
> > > > > > > that
> > > > > > > it doesn't function how I understood it would.   (Why only 
> > > > > > > once
> > per
> > > > > > > thread-group?!)
> > > > > > >
> > > > > > > I need to reassess my approach :  a BeanShell Sampler
> > > > > > > producing something for a ForEach Controller looks likely.
> > > > > > >
> > > > > > > Thanks again.
> > > > > > >
> > > > > > > Nige
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Flavio Cysne [mailto:flaviocysne@gmail.com
> <javascript:;>]
> > > > > > > Sent: Friday, 15 May 2015 8:31 PM
> > > > > > > To: JMeter Users List
> > > > > > > Subject: Re: Loop controller behaviour
> > > > > > >
> > > > > > > Nice,
> > > > > > >
> > > > > > >     I forgot to mention that CSV Dataset config don't go
> > > > > > > to the
> > > next
> > > > > > > line when using loop controller. In your case, just when
> > > > > > > using
> > Test
> > > > > > > Plan's Loop count.
> > > > > > >
> > > > > > > Hope it helps.
> > > > > > >
> > > > > > >
> > > ------------------------------------------------------------------
> > > ---
> > > > > > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> <javascript:;>
> > > > > > > For additional commands, e-mail:
> > > > > > > user-help@jmeter.apache.org
> <javascript:;>
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> <javascript:;>
> > > > > For additional commands, e-mail: user-help@jmeter.apache.org
> <javascript:;>
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Regards,
> > > > Pravesh prajapati.
> > > > Mob:-9702600170
> > > >
> > >
> > >
> > >
> > > --
> > > Thanks,
> > > MAhesh
> > >
> >
> >
> >
> > --
> > Regards,
> > Pravesh prajapati.
> > Mob:-9702600170
> >
>
>
>
> --
> Thanks,
> MAhesh
>


--
Regards,
Pravesh prajapati.
Mob:-9702600170

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org


Re: Loop controller behaviour

Posted by Pravesh Prajapati <pr...@gmail.com>.
Hi mahesh,
I is it compulsory to to keep the jmx file on the slave machine.
What is did is I started jmeter server on both slave and added the ip's of
slave mc into jmeter.properties file on master mc.
now I executed the script from master on both slave.

but I didn't any thing on slave mc.
if I need to keep jmx file on slave so where should I keep it.

can you please let me know where logs are generated on salve and master mc
so that I can just analyse that.

please reply.

Thanks in advance.


On Wednesday, May 20, 2015, mahesh bhasme <mb...@gmail.com> wrote:

> Yes..you can use GUI mode and get aggregate report. just keep jmx file on
> both slave at same location and follow steps from given link
>
> Thanks,
> Mahesh
>
> On Tue, May 19, 2015 at 8:08 PM, Pravesh Prajapati <
> prajapati.pravesh@gmail.com <javascript:;>> wrote:
>
> > Hi Mahesh,
> > Can we do that using GUI mode.
> > Say for example I have one master & I have added Aggregate report
> listener
> > to it with the script.
> > Now I am Distributing the loads on slave machine eg:-slave1=500 VU &
> > slave2:-200 VU.
> > Then can I get Consolidated reports from these two slaves on the Master
> > machines listener.
> > Please reply.
> > Thanks in Advance.
> > Please call on the mob no 9702600170, OR give a miss call I will cal you.
> >
> >
> > Regards,
> > Pravesh
> >
> >
> > On Tue, May 19, 2015 at 7:25 PM, mahesh bhasme <mbhasme@gmail.com
> <javascript:;>> wrote:
> >
> > > Hi Pravesh,
> > >
> > > You can use aggregate report to collect result from slaves. Following
> > > reference ulr has steps to configure master/slave jmeter.
> > >
> > >
> >
> http://myloadtesting.blogspot.in/2014/11/jmeter-setup-for-aggregate-results.html
> > >
> > >
> > > Thanks,
> > > Mahesh
> > > http://myloadtesting.blogspot.in/
> > >
> > > On Tue, May 19, 2015 at 6:19 PM, Pravesh Prajapati <
> > > prajapati.pravesh@gmail.com <javascript:;>> wrote:
> > >
> > > > Hi Sir,
> > > >
> > > > Can you please provide me solution regarding to master slave
> > > architecture.
> > > >
> > > > Say for eg:-
> > > >
> > > > I have one master machine & three slave machine.
> > > >
> > > > I have distributed load on these three slave machines are as follows.
> > > >
> > > > 1000 vu on slave first, 2000 vu on slave 2nd & 2500 vu on slave 3rd.
> > > >
> > > > Now can I have a consolidate report for 5500 VU  form Master machine.
> > > >
> > > > OR Is there is any mechanism from where we can consolidate the report
> > for
> > > > these distributed users into Jmeter.
> > > >
> > > > Sir, one more question.
> > > >
> > > > What is the minimum hardware configuration required for running 1000
> vu
> > > on
> > > > Slave machine.
> > > >
> > > >
> > > > Please reply.
> > > > Thanks in Advance.
> > > >
> > > > On Tue, May 19, 2015 at 6:31 AM, Nigel Donaldson <
> > ndonaldson@aconex.com <javascript:;>>
> > > > wrote:
> > > >
> > > > > I appreciate your effort, Flavio.
> > > > >
> > > > > I also created a new minimal Test Plan yesterday, using the same
> > JMeter
> > > > > logic/elements I'd flagged, but using different, fixed values for
> the
> > > > > 'Fields' variable (still coming from a CSV source).  It exhibited
> > > similar
> > > > > behaviour to what was happening in my 'real' Test Plan: the Loop
> > > > Controller
> > > > > was never working beyond the first iteration in any Thread Group.
> > > > >
> > > > > Cutting my losses, I reworked the Test Plan by replacing the If /
> > Loop
> > > /
> > > > > Counter trinity with a BeanShell Sampler / ForEach Controller duo.
> > > > >
> > > > > Functionality is now what I expect, in that _all_ iterations in
> _all_
> > > > > Thread
> > > > > Groups now correctly 'loop over' their respective number of fields.
> > > > >
> > > > > Nige
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Flavio Cysne [mailto:flaviocysne@gmail.com <javascript:;>]
> > > > > > Sent: Monday, 18 May 2015 11:11 PM
> > > > > > To: JMeter Users List
> > > > > > Subject: RE: Loop controller behaviour
> > > > > >
> > > > > > Nigel,
> > > > > >
> > > > > >     I published a script in pastebin,
> > > > > > http://pastebin.com/download.php?i=bL7kwXjA, using a Thread
> Group
> > > with
> > > > > > the logic you mentioned and another Thread Group using a Test
> > > Fragment
> > > > as
> > > > > > well.
> > > > > > ATM it is not using a CSV dataset nor the dynamic values per
> user,
> > as
> > > > you
> > > > > > said.
> > > > > >
> > > > > > Hope it helps.
> > > > > > Em 18/05/2015 00:39, "Nigel Donaldson" <ndonaldson@aconex.com
> <javascript:;>>
> > > > > > escreveu:
> > > > > >
> > > > > > > Hello, Flavio.
> > > > > > >
> > > > > > > I have to admit I didn't comprehend your statement per se,
> given
> > > that
> > > > > > > my CSV
> > > > > > > entries _are_ being used correctly.   However, it eventually
> lead
> > > me
> > > > to
> > > > > > > revisit the documentation for Loop Controller, and I've just
> > > realised
> > > > > > > that
> > > > > > > it doesn't function how I understood it would.   (Why only once
> > per
> > > > > > > thread-group?!)
> > > > > > >
> > > > > > > I need to reassess my approach :  a BeanShell Sampler producing
> > > > > > > something for a ForEach Controller looks likely.
> > > > > > >
> > > > > > > Thanks again.
> > > > > > >
> > > > > > > Nige
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Flavio Cysne [mailto:flaviocysne@gmail.com
> <javascript:;>]
> > > > > > > Sent: Friday, 15 May 2015 8:31 PM
> > > > > > > To: JMeter Users List
> > > > > > > Subject: Re: Loop controller behaviour
> > > > > > >
> > > > > > > Nice,
> > > > > > >
> > > > > > >     I forgot to mention that CSV Dataset config don't go to the
> > > next
> > > > > > > line when using loop controller. In your case, just when using
> > Test
> > > > > > > Plan's Loop count.
> > > > > > >
> > > > > > > Hope it helps.
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> <javascript:;>
> > > > > > > For additional commands, e-mail: user-help@jmeter.apache.org
> <javascript:;>
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> <javascript:;>
> > > > > For additional commands, e-mail: user-help@jmeter.apache.org
> <javascript:;>
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Regards,
> > > > Pravesh prajapati.
> > > > Mob:-9702600170
> > > >
> > >
> > >
> > >
> > > --
> > > Thanks,
> > > MAhesh
> > >
> >
> >
> >
> > --
> > Regards,
> > Pravesh prajapati.
> > Mob:-9702600170
> >
>
>
>
> --
> Thanks,
> MAhesh
>


-- 
Regards,
Pravesh prajapati.
Mob:-9702600170

Re: Loop controller behaviour

Posted by mahesh bhasme <mb...@gmail.com>.
Yes..you can use GUI mode and get aggregate report. just keep jmx file on
both slave at same location and follow steps from given link

Thanks,
Mahesh

On Tue, May 19, 2015 at 8:08 PM, Pravesh Prajapati <
prajapati.pravesh@gmail.com> wrote:

> Hi Mahesh,
> Can we do that using GUI mode.
> Say for example I have one master & I have added Aggregate report listener
> to it with the script.
> Now I am Distributing the loads on slave machine eg:-slave1=500 VU &
> slave2:-200 VU.
> Then can I get Consolidated reports from these two slaves on the Master
> machines listener.
> Please reply.
> Thanks in Advance.
> Please call on the mob no 9702600170, OR give a miss call I will cal you.
>
>
> Regards,
> Pravesh
>
>
> On Tue, May 19, 2015 at 7:25 PM, mahesh bhasme <mb...@gmail.com> wrote:
>
> > Hi Pravesh,
> >
> > You can use aggregate report to collect result from slaves. Following
> > reference ulr has steps to configure master/slave jmeter.
> >
> >
> http://myloadtesting.blogspot.in/2014/11/jmeter-setup-for-aggregate-results.html
> >
> >
> > Thanks,
> > Mahesh
> > http://myloadtesting.blogspot.in/
> >
> > On Tue, May 19, 2015 at 6:19 PM, Pravesh Prajapati <
> > prajapati.pravesh@gmail.com> wrote:
> >
> > > Hi Sir,
> > >
> > > Can you please provide me solution regarding to master slave
> > architecture.
> > >
> > > Say for eg:-
> > >
> > > I have one master machine & three slave machine.
> > >
> > > I have distributed load on these three slave machines are as follows.
> > >
> > > 1000 vu on slave first, 2000 vu on slave 2nd & 2500 vu on slave 3rd.
> > >
> > > Now can I have a consolidate report for 5500 VU  form Master machine.
> > >
> > > OR Is there is any mechanism from where we can consolidate the report
> for
> > > these distributed users into Jmeter.
> > >
> > > Sir, one more question.
> > >
> > > What is the minimum hardware configuration required for running 1000 vu
> > on
> > > Slave machine.
> > >
> > >
> > > Please reply.
> > > Thanks in Advance.
> > >
> > > On Tue, May 19, 2015 at 6:31 AM, Nigel Donaldson <
> ndonaldson@aconex.com>
> > > wrote:
> > >
> > > > I appreciate your effort, Flavio.
> > > >
> > > > I also created a new minimal Test Plan yesterday, using the same
> JMeter
> > > > logic/elements I'd flagged, but using different, fixed values for the
> > > > 'Fields' variable (still coming from a CSV source).  It exhibited
> > similar
> > > > behaviour to what was happening in my 'real' Test Plan: the Loop
> > > Controller
> > > > was never working beyond the first iteration in any Thread Group.
> > > >
> > > > Cutting my losses, I reworked the Test Plan by replacing the If /
> Loop
> > /
> > > > Counter trinity with a BeanShell Sampler / ForEach Controller duo.
> > > >
> > > > Functionality is now what I expect, in that _all_ iterations in _all_
> > > > Thread
> > > > Groups now correctly 'loop over' their respective number of fields.
> > > >
> > > > Nige
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Flavio Cysne [mailto:flaviocysne@gmail.com]
> > > > > Sent: Monday, 18 May 2015 11:11 PM
> > > > > To: JMeter Users List
> > > > > Subject: RE: Loop controller behaviour
> > > > >
> > > > > Nigel,
> > > > >
> > > > >     I published a script in pastebin,
> > > > > http://pastebin.com/download.php?i=bL7kwXjA, using a Thread Group
> > with
> > > > > the logic you mentioned and another Thread Group using a Test
> > Fragment
> > > as
> > > > > well.
> > > > > ATM it is not using a CSV dataset nor the dynamic values per user,
> as
> > > you
> > > > > said.
> > > > >
> > > > > Hope it helps.
> > > > > Em 18/05/2015 00:39, "Nigel Donaldson" <nd...@aconex.com>
> > > > > escreveu:
> > > > >
> > > > > > Hello, Flavio.
> > > > > >
> > > > > > I have to admit I didn't comprehend your statement per se, given
> > that
> > > > > > my CSV
> > > > > > entries _are_ being used correctly.   However, it eventually lead
> > me
> > > to
> > > > > > revisit the documentation for Loop Controller, and I've just
> > realised
> > > > > > that
> > > > > > it doesn't function how I understood it would.   (Why only once
> per
> > > > > > thread-group?!)
> > > > > >
> > > > > > I need to reassess my approach :  a BeanShell Sampler producing
> > > > > > something for a ForEach Controller looks likely.
> > > > > >
> > > > > > Thanks again.
> > > > > >
> > > > > > Nige
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Flavio Cysne [mailto:flaviocysne@gmail.com]
> > > > > > Sent: Friday, 15 May 2015 8:31 PM
> > > > > > To: JMeter Users List
> > > > > > Subject: Re: Loop controller behaviour
> > > > > >
> > > > > > Nice,
> > > > > >
> > > > > >     I forgot to mention that CSV Dataset config don't go to the
> > next
> > > > > > line when using loop controller. In your case, just when using
> Test
> > > > > > Plan's Loop count.
> > > > > >
> > > > > > Hope it helps.
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > > > > > For additional commands, e-mail: user-help@jmeter.apache.org
> > > > > >
> > > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > > > For additional commands, e-mail: user-help@jmeter.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > Regards,
> > > Pravesh prajapati.
> > > Mob:-9702600170
> > >
> >
> >
> >
> > --
> > Thanks,
> > MAhesh
> >
>
>
>
> --
> Regards,
> Pravesh prajapati.
> Mob:-9702600170
>



-- 
Thanks,
MAhesh

Re: Loop controller behaviour

Posted by Pravesh Prajapati <pr...@gmail.com>.
Hi Mahesh,
Can we do that using GUI mode.
Say for example I have one master & I have added Aggregate report listener
to it with the script.
Now I am Distributing the loads on slave machine eg:-slave1=500 VU &
slave2:-200 VU.
Then can I get Consolidated reports from these two slaves on the Master
machines listener.
Please reply.
Thanks in Advance.
Please call on the mob no 9702600170, OR give a miss call I will cal you.


Regards,
Pravesh


On Tue, May 19, 2015 at 7:25 PM, mahesh bhasme <mb...@gmail.com> wrote:

> Hi Pravesh,
>
> You can use aggregate report to collect result from slaves. Following
> reference ulr has steps to configure master/slave jmeter.
>
> http://myloadtesting.blogspot.in/2014/11/jmeter-setup-for-aggregate-results.html
>
>
> Thanks,
> Mahesh
> http://myloadtesting.blogspot.in/
>
> On Tue, May 19, 2015 at 6:19 PM, Pravesh Prajapati <
> prajapati.pravesh@gmail.com> wrote:
>
> > Hi Sir,
> >
> > Can you please provide me solution regarding to master slave
> architecture.
> >
> > Say for eg:-
> >
> > I have one master machine & three slave machine.
> >
> > I have distributed load on these three slave machines are as follows.
> >
> > 1000 vu on slave first, 2000 vu on slave 2nd & 2500 vu on slave 3rd.
> >
> > Now can I have a consolidate report for 5500 VU  form Master machine.
> >
> > OR Is there is any mechanism from where we can consolidate the report for
> > these distributed users into Jmeter.
> >
> > Sir, one more question.
> >
> > What is the minimum hardware configuration required for running 1000 vu
> on
> > Slave machine.
> >
> >
> > Please reply.
> > Thanks in Advance.
> >
> > On Tue, May 19, 2015 at 6:31 AM, Nigel Donaldson <nd...@aconex.com>
> > wrote:
> >
> > > I appreciate your effort, Flavio.
> > >
> > > I also created a new minimal Test Plan yesterday, using the same JMeter
> > > logic/elements I'd flagged, but using different, fixed values for the
> > > 'Fields' variable (still coming from a CSV source).  It exhibited
> similar
> > > behaviour to what was happening in my 'real' Test Plan: the Loop
> > Controller
> > > was never working beyond the first iteration in any Thread Group.
> > >
> > > Cutting my losses, I reworked the Test Plan by replacing the If / Loop
> /
> > > Counter trinity with a BeanShell Sampler / ForEach Controller duo.
> > >
> > > Functionality is now what I expect, in that _all_ iterations in _all_
> > > Thread
> > > Groups now correctly 'loop over' their respective number of fields.
> > >
> > > Nige
> > >
> > >
> > > > -----Original Message-----
> > > > From: Flavio Cysne [mailto:flaviocysne@gmail.com]
> > > > Sent: Monday, 18 May 2015 11:11 PM
> > > > To: JMeter Users List
> > > > Subject: RE: Loop controller behaviour
> > > >
> > > > Nigel,
> > > >
> > > >     I published a script in pastebin,
> > > > http://pastebin.com/download.php?i=bL7kwXjA, using a Thread Group
> with
> > > > the logic you mentioned and another Thread Group using a Test
> Fragment
> > as
> > > > well.
> > > > ATM it is not using a CSV dataset nor the dynamic values per user, as
> > you
> > > > said.
> > > >
> > > > Hope it helps.
> > > > Em 18/05/2015 00:39, "Nigel Donaldson" <nd...@aconex.com>
> > > > escreveu:
> > > >
> > > > > Hello, Flavio.
> > > > >
> > > > > I have to admit I didn't comprehend your statement per se, given
> that
> > > > > my CSV
> > > > > entries _are_ being used correctly.   However, it eventually lead
> me
> > to
> > > > > revisit the documentation for Loop Controller, and I've just
> realised
> > > > > that
> > > > > it doesn't function how I understood it would.   (Why only once per
> > > > > thread-group?!)
> > > > >
> > > > > I need to reassess my approach :  a BeanShell Sampler producing
> > > > > something for a ForEach Controller looks likely.
> > > > >
> > > > > Thanks again.
> > > > >
> > > > > Nige
> > > > >
> > > > > -----Original Message-----
> > > > > From: Flavio Cysne [mailto:flaviocysne@gmail.com]
> > > > > Sent: Friday, 15 May 2015 8:31 PM
> > > > > To: JMeter Users List
> > > > > Subject: Re: Loop controller behaviour
> > > > >
> > > > > Nice,
> > > > >
> > > > >     I forgot to mention that CSV Dataset config don't go to the
> next
> > > > > line when using loop controller. In your case, just when using Test
> > > > > Plan's Loop count.
> > > > >
> > > > > Hope it helps.
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > > > > For additional commands, e-mail: user-help@jmeter.apache.org
> > > > >
> > > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > > For additional commands, e-mail: user-help@jmeter.apache.org
> > >
> > >
> >
> >
> > --
> > Regards,
> > Pravesh prajapati.
> > Mob:-9702600170
> >
>
>
>
> --
> Thanks,
> MAhesh
>



-- 
Regards,
Pravesh prajapati.
Mob:-9702600170

Re: Loop controller behaviour

Posted by mahesh bhasme <mb...@gmail.com>.
Hi Pravesh,

You can use aggregate report to collect result from slaves. Following
reference ulr has steps to configure master/slave jmeter.
http://myloadtesting.blogspot.in/2014/11/jmeter-setup-for-aggregate-results.html


Thanks,
Mahesh
http://myloadtesting.blogspot.in/

On Tue, May 19, 2015 at 6:19 PM, Pravesh Prajapati <
prajapati.pravesh@gmail.com> wrote:

> Hi Sir,
>
> Can you please provide me solution regarding to master slave architecture.
>
> Say for eg:-
>
> I have one master machine & three slave machine.
>
> I have distributed load on these three slave machines are as follows.
>
> 1000 vu on slave first, 2000 vu on slave 2nd & 2500 vu on slave 3rd.
>
> Now can I have a consolidate report for 5500 VU  form Master machine.
>
> OR Is there is any mechanism from where we can consolidate the report for
> these distributed users into Jmeter.
>
> Sir, one more question.
>
> What is the minimum hardware configuration required for running 1000 vu on
> Slave machine.
>
>
> Please reply.
> Thanks in Advance.
>
> On Tue, May 19, 2015 at 6:31 AM, Nigel Donaldson <nd...@aconex.com>
> wrote:
>
> > I appreciate your effort, Flavio.
> >
> > I also created a new minimal Test Plan yesterday, using the same JMeter
> > logic/elements I'd flagged, but using different, fixed values for the
> > 'Fields' variable (still coming from a CSV source).  It exhibited similar
> > behaviour to what was happening in my 'real' Test Plan: the Loop
> Controller
> > was never working beyond the first iteration in any Thread Group.
> >
> > Cutting my losses, I reworked the Test Plan by replacing the If / Loop /
> > Counter trinity with a BeanShell Sampler / ForEach Controller duo.
> >
> > Functionality is now what I expect, in that _all_ iterations in _all_
> > Thread
> > Groups now correctly 'loop over' their respective number of fields.
> >
> > Nige
> >
> >
> > > -----Original Message-----
> > > From: Flavio Cysne [mailto:flaviocysne@gmail.com]
> > > Sent: Monday, 18 May 2015 11:11 PM
> > > To: JMeter Users List
> > > Subject: RE: Loop controller behaviour
> > >
> > > Nigel,
> > >
> > >     I published a script in pastebin,
> > > http://pastebin.com/download.php?i=bL7kwXjA, using a Thread Group with
> > > the logic you mentioned and another Thread Group using a Test Fragment
> as
> > > well.
> > > ATM it is not using a CSV dataset nor the dynamic values per user, as
> you
> > > said.
> > >
> > > Hope it helps.
> > > Em 18/05/2015 00:39, "Nigel Donaldson" <nd...@aconex.com>
> > > escreveu:
> > >
> > > > Hello, Flavio.
> > > >
> > > > I have to admit I didn't comprehend your statement per se, given that
> > > > my CSV
> > > > entries _are_ being used correctly.   However, it eventually lead me
> to
> > > > revisit the documentation for Loop Controller, and I've just realised
> > > > that
> > > > it doesn't function how I understood it would.   (Why only once per
> > > > thread-group?!)
> > > >
> > > > I need to reassess my approach :  a BeanShell Sampler producing
> > > > something for a ForEach Controller looks likely.
> > > >
> > > > Thanks again.
> > > >
> > > > Nige
> > > >
> > > > -----Original Message-----
> > > > From: Flavio Cysne [mailto:flaviocysne@gmail.com]
> > > > Sent: Friday, 15 May 2015 8:31 PM
> > > > To: JMeter Users List
> > > > Subject: Re: Loop controller behaviour
> > > >
> > > > Nice,
> > > >
> > > >     I forgot to mention that CSV Dataset config don't go to the next
> > > > line when using loop controller. In your case, just when using Test
> > > > Plan's Loop count.
> > > >
> > > > Hope it helps.
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > > > For additional commands, e-mail: user-help@jmeter.apache.org
> > > >
> > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > For additional commands, e-mail: user-help@jmeter.apache.org
> >
> >
>
>
> --
> Regards,
> Pravesh prajapati.
> Mob:-9702600170
>



-- 
Thanks,
MAhesh

Re: Loop controller behaviour

Posted by Pravesh Prajapati <pr...@gmail.com>.
Hi Sir,

Can you please provide me solution regarding to master slave architecture.

Say for eg:-

I have one master machine & three slave machine.

I have distributed load on these three slave machines are as follows.

1000 vu on slave first, 2000 vu on slave 2nd & 2500 vu on slave 3rd.

Now can I have a consolidate report for 5500 VU  form Master machine.

OR Is there is any mechanism from where we can consolidate the report for
these distributed users into Jmeter.

Sir, one more question.

What is the minimum hardware configuration required for running 1000 vu on
Slave machine.


Please reply.
Thanks in Advance.

On Tue, May 19, 2015 at 6:31 AM, Nigel Donaldson <nd...@aconex.com>
wrote:

> I appreciate your effort, Flavio.
>
> I also created a new minimal Test Plan yesterday, using the same JMeter
> logic/elements I'd flagged, but using different, fixed values for the
> 'Fields' variable (still coming from a CSV source).  It exhibited similar
> behaviour to what was happening in my 'real' Test Plan: the Loop Controller
> was never working beyond the first iteration in any Thread Group.
>
> Cutting my losses, I reworked the Test Plan by replacing the If / Loop /
> Counter trinity with a BeanShell Sampler / ForEach Controller duo.
>
> Functionality is now what I expect, in that _all_ iterations in _all_
> Thread
> Groups now correctly 'loop over' their respective number of fields.
>
> Nige
>
>
> > -----Original Message-----
> > From: Flavio Cysne [mailto:flaviocysne@gmail.com]
> > Sent: Monday, 18 May 2015 11:11 PM
> > To: JMeter Users List
> > Subject: RE: Loop controller behaviour
> >
> > Nigel,
> >
> >     I published a script in pastebin,
> > http://pastebin.com/download.php?i=bL7kwXjA, using a Thread Group with
> > the logic you mentioned and another Thread Group using a Test Fragment as
> > well.
> > ATM it is not using a CSV dataset nor the dynamic values per user, as you
> > said.
> >
> > Hope it helps.
> > Em 18/05/2015 00:39, "Nigel Donaldson" <nd...@aconex.com>
> > escreveu:
> >
> > > Hello, Flavio.
> > >
> > > I have to admit I didn't comprehend your statement per se, given that
> > > my CSV
> > > entries _are_ being used correctly.   However, it eventually lead me to
> > > revisit the documentation for Loop Controller, and I've just realised
> > > that
> > > it doesn't function how I understood it would.   (Why only once per
> > > thread-group?!)
> > >
> > > I need to reassess my approach :  a BeanShell Sampler producing
> > > something for a ForEach Controller looks likely.
> > >
> > > Thanks again.
> > >
> > > Nige
> > >
> > > -----Original Message-----
> > > From: Flavio Cysne [mailto:flaviocysne@gmail.com]
> > > Sent: Friday, 15 May 2015 8:31 PM
> > > To: JMeter Users List
> > > Subject: Re: Loop controller behaviour
> > >
> > > Nice,
> > >
> > >     I forgot to mention that CSV Dataset config don't go to the next
> > > line when using loop controller. In your case, just when using Test
> > > Plan's Loop count.
> > >
> > > Hope it helps.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > > For additional commands, e-mail: user-help@jmeter.apache.org
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>


-- 
Regards,
Pravesh prajapati.
Mob:-9702600170

RE: Loop controller behaviour

Posted by Nigel Donaldson <nd...@aconex.com>.
I appreciate your effort, Flavio.

I also created a new minimal Test Plan yesterday, using the same JMeter 
logic/elements I'd flagged, but using different, fixed values for the 
'Fields' variable (still coming from a CSV source).  It exhibited similar 
behaviour to what was happening in my 'real' Test Plan: the Loop Controller 
was never working beyond the first iteration in any Thread Group.

Cutting my losses, I reworked the Test Plan by replacing the If / Loop / 
Counter trinity with a BeanShell Sampler / ForEach Controller duo.

Functionality is now what I expect, in that _all_ iterations in _all_ Thread 
Groups now correctly 'loop over' their respective number of fields.

Nige


> -----Original Message-----
> From: Flavio Cysne [mailto:flaviocysne@gmail.com]
> Sent: Monday, 18 May 2015 11:11 PM
> To: JMeter Users List
> Subject: RE: Loop controller behaviour
>
> Nigel,
>
>     I published a script in pastebin,
> http://pastebin.com/download.php?i=bL7kwXjA, using a Thread Group with
> the logic you mentioned and another Thread Group using a Test Fragment as
> well.
> ATM it is not using a CSV dataset nor the dynamic values per user, as you
> said.
>
> Hope it helps.
> Em 18/05/2015 00:39, "Nigel Donaldson" <nd...@aconex.com>
> escreveu:
>
> > Hello, Flavio.
> >
> > I have to admit I didn't comprehend your statement per se, given that
> > my CSV
> > entries _are_ being used correctly.   However, it eventually lead me to
> > revisit the documentation for Loop Controller, and I've just realised 
> > that
> > it doesn't function how I understood it would.   (Why only once per
> > thread-group?!)
> >
> > I need to reassess my approach :  a BeanShell Sampler producing
> > something for a ForEach Controller looks likely.
> >
> > Thanks again.
> >
> > Nige
> >
> > -----Original Message-----
> > From: Flavio Cysne [mailto:flaviocysne@gmail.com]
> > Sent: Friday, 15 May 2015 8:31 PM
> > To: JMeter Users List
> > Subject: Re: Loop controller behaviour
> >
> > Nice,
> >
> >     I forgot to mention that CSV Dataset config don't go to the next
> > line when using loop controller. In your case, just when using Test
> > Plan's Loop count.
> >
> > Hope it helps.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > For additional commands, e-mail: user-help@jmeter.apache.org
> >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org


RE: Loop controller behaviour

Posted by Flavio Cysne <fl...@gmail.com>.
Nigel,

    I published a script in pastebin,
http://pastebin.com/download.php?i=bL7kwXjA, using a Thread Group with the
logic you mentioned and another Thread Group using a Test Fragment as well.
ATM it is not using a CSV dataset nor the dynamic values per user, as you
said.

Hope it helps.
Em 18/05/2015 00:39, "Nigel Donaldson" <nd...@aconex.com> escreveu:

> Hello, Flavio.
>
> I have to admit I didn't comprehend your statement per se, given that my
> CSV
> entries _are_ being used correctly.   However, it eventually lead me to
> revisit the documentation for Loop Controller, and I've just realised that
> it doesn't function how I understood it would.   (Why only once per
> thread-group?!)
>
> I need to reassess my approach :  a BeanShell Sampler producing something
> for a ForEach Controller looks likely.
>
> Thanks again.
>
> Nige
>
> -----Original Message-----
> From: Flavio Cysne [mailto:flaviocysne@gmail.com]
> Sent: Friday, 15 May 2015 8:31 PM
> To: JMeter Users List
> Subject: Re: Loop controller behaviour
>
> Nice,
>
>     I forgot to mention that CSV Dataset config don't go to the next line
> when using loop controller. In your case, just when using Test Plan's Loop
> count.
>
> Hope it helps.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>

RE: Loop controller behaviour

Posted by Nigel Donaldson <nd...@aconex.com>.
Hello, Flavio.

I have to admit I didn't comprehend your statement per se, given that my CSV 
entries _are_ being used correctly.   However, it eventually lead me to 
revisit the documentation for Loop Controller, and I've just realised that 
it doesn't function how I understood it would.   (Why only once per 
thread-group?!)

I need to reassess my approach :  a BeanShell Sampler producing something 
for a ForEach Controller looks likely.

Thanks again.

Nige

-----Original Message-----
From: Flavio Cysne [mailto:flaviocysne@gmail.com]
Sent: Friday, 15 May 2015 8:31 PM
To: JMeter Users List
Subject: Re: Loop controller behaviour

Nice,

    I forgot to mention that CSV Dataset config don't go to the next line 
when using loop controller. In your case, just when using Test Plan's Loop 
count.

Hope it helps.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org


Re: Loop controller behaviour

Posted by Flavio Cysne <fl...@gmail.com>.
Nice,

    I forgot to mention that CSV Dataset config don't go to the next line
when using loop controller. In your case, just when using Test Plan's Loop
count.

Hope it helps.

RE: Loop controller behaviour

Posted by Nigel Donaldson <nd...@aconex.com>.
Flavio,  thanks for responding here and in a second mail.   Sorry, my Test 
Plan is very large, and quite complicated.   I tried to simplify it by 
omitting anything I believed to be unnecessary (which I depict with 
ellipses), but evidently what I posted wasn't clear.

1)  The essence of Test Fragment XYZ is:

- Test Fragment XYZ
-- CSV Data
...
-- RegExp Extractor ( refName: 'Fields' )
...
-- If Controller ( condition: "${Fields_matchNr}"!="0" )
--- BeanShell Sampler #1
--- Loop Controller ( count: ${Fields_matchNr} )
---- BeanShell Sampler #2
---- Counter ( start: 1, max: ${Fields_matchNr} )
---- BeanShell Sampler #3
---- HTTP Request
---- BeanShell Sampler #4
--- BeanShell Sampler #5
...

2)  This Test Fragment is referenced by a Module Controller as the only item 
of a Thread Group.  (This structure might be odd, but there's a reason for 
it, too long-winded to detail here).
3)  The 'Fields' array stems from a Regular Expression Extractor before the 
If Controller in the Fragment (now shown above).
4)  I used five BeanShell Samplers to show what part of the Fragment is 
executed, and to print ${Fields_matchNr} - it contains the correct/expected 
number in each case (please see the logs in the original post).
5)  The data drawn from the CSV is as expected.

To stress: this Fragment works fine when the Thread Group has N threads and 
a Thread Group loop count (ie. iteration count) of one:  I've called this 
'concurrent execution' of N users.

However, when I specify one thread and N iterations for that thread (which 
I've called 'sequential execution' of the same N users), the Loop Controller 
of the Fragment is executed only for the first iteration, but not for 
iterations 2..N.

I don't know why, and it's a bit of a show-stopper for me.

Nige


-----Original Message-----
From: Flavio Cysne [mailto:flaviocysne@gmail.com]
Sent: Friday, 15 May 2015 8:26 PM
To: JMeter Users List
Subject: Re: Loop controller behaviour

Nige,

     what`s inside TestFragment XYZ? Is there any relationship betweeen this 
fragment and the Test Plan presented?
     Where in the script is Fields_matchNr initialized?

     I suggest you to "print" the ${Fields_matchNr} value to check if it has 
an unexpected content.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org


Re: Loop controller behaviour

Posted by Flavio Cysne <fl...@gmail.com>.
Nige,

     what`s inside TestFragment XYZ? Is there any relationship betweeen
this fragment and the Test Plan presented?
     Where in the script is Fields_matchNr initialized?

     I suggest you to "print" the ${Fields_matchNr} value to check if it
has an unexpected content.

Re: Loop controller behaviour

Posted by Nigel Donaldson <nd...@aconex.com>.
Oh, observed with both JMeter 2.11 and 2.13. 

Nige 

----- Original Message -----

From: "Nigel Donaldson" <nd...@aconex.com> 
To: user@jmeter.apache.org 
Sent: Wednesday, 13 May, 2015 3:27:16 PM 
Subject: Loop controller behaviour 

I have the following arrangement (BeanShell samplers added solely for 
debugging purposes): 



Test Plan 

... 

- Test Fragment XYZ 

-- CSV Data 

... 

-- If Controller ( condition: "${Fields_matchNr}"!="0" ) 

--- BeanShell Sampler #1 

--- Loop Controller ( count: ${Fields_matchNr} ) 

---- BeanShell Sampler #2 

---- Counter ( start: 1, max: ${Fields_matchNr} ) 

---- BeanShell Sampler #3 

---- HTTP Request 

---- BeanShell Sampler #4 

--- BeanShell Sampler #5 

... 

- Thread Group 

- ModuleController ( -> Test Fragment XYZ ) 





User data is drawn from the CSV file. The run-time variable 
Fields_matchNr , extracted earlier, has a value of 1 for the first user, 
and 2 for the second user (it will have a value between 1 and 4 for other 
users, but is not known until run-time). 





I'm perplexed by my observation of differing behaviour of the loop 
controller in two slightly different executions of the test-plan. 





Concurrent execution: if I initially specify 2 threads with 1 iteration, 
the following expected outcome is observed: 



2015/05/13 14:46:55 INFO - jmeter.engine.StandardJMeterEngine: Running 
the test! 

... 

2015/05/13 14:46:55 INFO - jmeter.gui.util.JMeterMenuBar: 
setRunning(true,*local*) 

2015/05/13 14:46:55 INFO - jmeter.engine.StandardJMeterEngine: Starting 
ThreadGroup: 1 : MailNew 

2015/05/13 14:46:55 INFO - jmeter.engine.StandardJMeterEngine: Starting 2 
threads for group MailNew. 

... 

2015/05/13 14:46:56 INFO - jmeter.threads.JMeterThread: Thread started: 
MailNew 1-1 

2015/05/13 14:46:56 INFO - jmeter.services.FileServer: Stored: 
./workload/MailNewUsers.dat Alias: ./workload/MailNewUsers.dat@1116508025 

... 

2015/05/13 14:47:05 INFO - jmeter.threads.JMeterThread: Thread started: 
MailNew 1-2 

2015/05/13 14:47:07 WARN - jmeter.util.BeanShellTestElement: Debug #1 : 
Fields_matchNr = 1 

2015/05/13 14:47:07 WARN - jmeter.util.BeanShellTestElement: Debug #2 : 
Fields_matchNr = 1 

2015/05/13 14:47:07 WARN - jmeter.util.BeanShellTestElement: Debug #3 : 
Fields_matchNr = 1 

2015/05/13 14:47:08 WARN - jmeter.util.BeanShellTestElement: Debug #4 : 
Fields_matchNr = 1 

2015/05/13 14:47:09 WARN - jmeter.util.BeanShellTestElement: Debug #5 : 
Fields_matchNr = 1 

2015/05/13 14:47:13 INFO - jmeter.threads.JMeterThread: Thread is done: 
MailNew 1-1 

2015/05/13 14:47:13 INFO - jmeter.threads.JMeterThread: Thread finished: 
MailNew 1-1 

2015/05/13 14:47:15 WARN - jmeter.util.BeanShellTestElement: Debug #1 : 
Fields_matchNr = 2 

2015/05/13 14:47:15 WARN - jmeter.util.BeanShellTestElement: Debug #2 : 
Fields_matchNr = 2 

2015/05/13 14:47:16 WARN - jmeter.util.BeanShellTestElement: Debug #3 : 
Fields_matchNr = 2 

2015/05/13 14:47:17 WARN - jmeter.util.BeanShellTestElement: Debug #4 : 
Fields_matchNr = 2 

2015/05/13 14:47:17 WARN - jmeter.util.BeanShellTestElement: Debug #2 : 
Fields_matchNr = 2 

2015/05/13 14:47:17 WARN - jmeter.util.BeanShellTestElement: Debug #3 : 
Fields_matchNr = 2 

2015/05/13 14:47:18 WARN - jmeter.util.BeanShellTestElement: Debug #4 : 
Fields_matchNr = 2 

2015/05/13 14:47:19 WARN - jmeter.util.BeanShellTestElement: Debug #5 : 
Fields_matchNr = 2 

2015/05/13 14:47:27 INFO - jmeter.threads.JMeterThread: Thread is done: 
MailNew 1-2 

2015/05/13 14:47:27 INFO - jmeter.threads.JMeterThread: Thread finished: 
MailNew 1-2 

2015/05/13 14:47:27 INFO - jmeter.engine.StandardJMeterEngine: Notifying 
test listeners of end of test 

2015/05/13 14:47:27 INFO - jmeter.services.FileServer: Close: 
./workload/MailNewUsers.dat@1116508025 

2015/05/13 14:47:27 INFO - jmeter.gui.util.JMeterMenuBar: 
setRunning(false,*local*) 





Sequential execution: when I change that to 1 thread with 2 iterations 
(with the same two users from the CSV file): 



2015/05/13 14:48:50 INFO - jmeter.engine.StandardJMeterEngine: Running 
the test! 

... 

2015/05/13 14:48:50 INFO - jmeter.gui.util.JMeterMenuBar: 
setRunning(true,*local*) 

2015/05/13 14:48:50 INFO - jmeter.engine.StandardJMeterEngine: Starting 
ThreadGroup: 1 : MailNew 

2015/05/13 14:48:50 INFO - jmeter.engine.StandardJMeterEngine: Starting 1 
threads for group MailNew. 

... 

2015/05/13 14:48:50 INFO - jmeter.threads.ThreadGroup: Starting thread 
group number 1 threads 1 ramp-up 19 perThread 19000.0 delayedStart=true 

2015/05/13 14:48:50 INFO - jmeter.threads.ThreadGroup: Started thread 
group number 1 

2015/05/13 14:48:50 INFO - jmeter.engine.StandardJMeterEngine: All thread 
groups have been started 

2015/05/13 14:48:50 INFO - jmeter.threads.JMeterThread: Thread started: 
MailNew 1-1 

2015/05/13 14:48:50 INFO - jmeter.services.FileServer: Stored: 
./workload/MailNewUsers.dat Alias: ./workload/MailNewUsers.dat@1800331312 

2015/05/13 14:49:00 WARN - jmeter.util.BeanShellTestElement: Debug #1 : 
Fields_matchNr = 1 

2015/05/13 14:49:01 WARN - jmeter.util.BeanShellTestElement: Debug #2 : 
Fields_matchNr = 1 

2015/05/13 14:49:01 WARN - jmeter.util.BeanShellTestElement: Debug #3 : 
Fields_matchNr = 1 

2015/05/13 14:49:02 WARN - jmeter.util.BeanShellTestElement: Debug #4 : 
Fields_matchNr = 1 

2015/05/13 14:49:02 WARN - jmeter.util.BeanShellTestElement: Debug #5 : 
Fields_matchNr = 1 

2015/05/13 14:49:15 WARN - jmeter.util.BeanShellTestElement: Debug #1 : 
Fields_matchNr = 2 

2015/05/13 14:49:16 WARN - jmeter.util.BeanShellTestElement: Debug #5 : 
Fields_matchNr = 2 

2015/05/13 14:49:22 ERROR - jmeter.util.BeanShellInterpreter: Error 
invoking bsh method: source Sourced file: ... 

... 

2015/05/13 14:49:24 INFO - jmeter.threads.JMeterThread: Thread is done: 
MailNew 1-1 

2015/05/13 14:49:24 INFO - jmeter.threads.JMeterThread: Thread finished: 
MailNew 1-1 

2015/05/13 14:49:24 INFO - jmeter.engine.StandardJMeterEngine: Notifying 
test listeners of end of test 

2015/05/13 14:49:24 INFO - jmeter.services.FileServer: Close: 
./workload/MailNewUsers.dat@1800331312 

2015/05/13 14:49:24 INFO - jmeter.gui.util.JMeterMenuBar: 
setRunning(false,*local*) 



For the second user (iteration), with the field-match being correct, there 
is no execution in the loop controller. Huh? (As a result, an essential 
variable is not set, and a subsequent beanshell pre-processor fails.) 





What am I missing here? Help appreciated. 





Regards, 



Nige