Hi sebb, You are correct, I meant to say 'thread groups' rather than threads. I managed to set the property, and pass it to the number of users field in the 2nd thread group - however, it only picks up the value every second time I execute the test plan. This has probably to do with the fact that I don't start the second thread group *after* the first one (they start simultaneously). When you say starting them consecutively, do you mean specifying a certain time at which the second thread group starts, using the scheduling mechanism ? Specifying a time is the only way I could think of controlling the startup behaviour of the thread groups... Please let me know if there is any other way.
Thanks for your help, hiro On Sun, 2009-02-22 at 22:31 +0000, sebb wrote: > On 22/02/2009, Hiro Protagonist <[email protected]> wrote: > > Hi all, > > > > I tried to dynamically set the number of users for the second thread in > > my test plan (based on how many results from a query in the first thread > > I find in the first) by giving ${__property(NUMBER_OF_CODES)} which > > seems to set the property value correctly > > The function __property() does not set a property. > > Did you mean _setProperty()? > > > - I can see the right number > > appear when using the debug sampler - and I can use this anywhere in the > > first thread, but when I try to specify the number of users in the > > second thread (in the "Number of Threads (users):" field) the thread > > doesn't get started ! > > I assume you mean you have two thread *groups* and you are trying to > use the result of running the first thread group to control the number > of threads in the second group. > > Is that correct? > > > Can this be done ? If so, how ? > > Works fine for me. > > Of course, you have to set the thread groups to run consecutively so > that the first group completes before the second one starts. > > > Thanks, > > hiro > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
