It would also be worth checking the jmeter.log file to see if there was some kind of error that caused the test to stop prematurely.
S. -----Original Message----- From: nlunebur [mailto:[EMAIL PROTECTED] Sent: 30 July 2004 00:06 To: JMeter Users List Subject: Re: Scheduler Duration Independable? i cannot recall exactly how we used the scheduler but i know that it worked perfectly fine using official 2.0.1 version. have you tried to set up your scheduler something like this?: start time: 2004/07/29 10:00:00 end time: 2004/07/29 11:00:00 and dont place any values in the duration. yeah there's something unclear with the scheduler but try this. goodluck! nicole Mallasee, Curt wrote: >Has anyone else experienced the duration element in the scheduler being very inaccurate? Example, I have a plan with one threadgroup that started at a specific time and with a duration of 3600 seconds (one hour). The test ended normally, but only 28 actual minutes elapsed. The scheduler appears to start accurately based on my system's clock. But the duration element appears not use the system clock and it seems to be using its own inaccurate mechanism. I have official version 2.0.1 > >Here was my plan setup: >Threadgroup: Threads= 1, loopcount=1, rampup=1, Scheduler start time 2004/07/29 10:00:00 duration: 3600 >-once only controller > -sample1 >-loop controller: infinite > -uniform random timer: 5000ms constant, 10000ms random > -sample2 > -sample3 > >--------------------------------------------------------------------- >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] _______________________________________________________ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. _______________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
