The login thread group should be disabled . you dont want it to run, thats why you are probably seeing the asynchronous login. Disabling the login thread group has no bearing when you include the Module controller I typically have reused ThreadGroup , Disabled +Simple Controlerr1 +++Steps for reusable func1 +Simple Controlerr2 +++Steps for reusable func2 ThreadGroup1 +Steps +ModuleController1 --> To SimpleController1 +Steps +ModuleController2 --> To SimpleController2
The moudle controller runs in context of the thread that includes it , so it wont be asynchronous. regards deepak On Tue, Mar 2, 2010 at 12:38 PM, daniel.green <[email protected]> wrote: > > > > daniel.green wrote: > > > > > > > > Deepak Shetty wrote: > >> > >> Look at the module and include controllers > >> > > > > I appreciate your response, it was was exactly what I was looking for. > > I... > > > > 1. Created a "login" thread group. > > 2. Added a module controller to each thread group that needed it > > 3. Pointed those controllers towards the login thread group > > > > Done! > > > > Whoops... I have a recording controller inside the thread group, yet still > it's executed asynchronously with the above setup. I want my thread group > to > wait while the "login" group finishes. How would I pull that off? > > -- > View this message in context: > http://old.nabble.com/Frequently-used-registration-login-sequence-tp27745956p27760871.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
