Each thread checks for the stop condition after each sampler, which is allowed to finish.
If you want to try experimenting, use the Java Request Sampler and set the time delay to a second or two. S. On 03/05/06, bgordon <[EMAIL PROTECTED]> wrote:
Ok, I have a threadGroup with a scheduler and a delay of 0 and a duration of 30. I am not seeing it stop after 30 seconds, or 5 minutes. When should it stop? Will it just knock existing http requests on the head and stop immediately? Will the current HTTP requests finish? Will each thread continue the current loop and then check to see if it should top after a pass through all the elements? In my test environment I have 200 threads and for each loop the thread group may take a while, so that could be a possible explanation. Thanks, Bruce sebb <[EMAIL PROTECTED]> wrote: On 02/05/06, bgordon wrote: > Ok (I have to admit you had me chuckling with your comment "I had lots of problems trying to get it to work... it did seem to work for me in some cases...".) > > I think my logic was wrong. If my ThreadGroup had a loop then the RuntimeController will only stop the elements nested within it. So using the Scheduler is preferred. In my case I want to > a. parameterize the duration from a property. Can I do that? I think so - try it. > b. follow your suggestion of setting a startup delay of 0, and a duration of 400 etc > I don't understand how to modify the Scheduler Configuration. Are the Start/Stop times required? In my case I don't care about the times-I want to run it ASAP, but with a delay. Do I want to parameterize the Start/end times or do I want to somehow leave them empty and simply set the duration and delay? If duration and Startup delay are set will the other fields be ignored? Yes, see the documentation ... http://jakarta.apache.org/jmeter/usermanual/component_reference.html#Thread_Group
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
