glad we can help.
peter
On Thu, 16 Dec 2004 10:35:38 -0000, Ashley Hayes
<[EMAIL PROTECTED]> wrote:
> My mistake, I miss interpreted my results ( my iteration can take quite a
> long time and was longer that the test duration ).
> So I can confirm that a start delay of 1 works for me, even with the start
> and end times as their default.
>
> For others out there the answer to my original question is that version
> 2.0.2 expects a Startup delay of > 0 to consider the Duration parameter.
>
> Thanks sebb/peter,
> A
>
> P.s.
> My new config is:
> Start Time is the default "1970/01/01 01:00:00"
> End Time is the default "1970/01/01 01:00:00"
> Duration (seconds) is ${TestDurationInSeconds}
> Startup delay (seconds) is 1
>
>
> -----Original Message-----
> From: sebb [mailto:[EMAIL PROTECTED]
> Sent: 15 December 2004 22:57
> To: JMeter Users List
> Subject: Re: Thread Group Scheduler 2.0.1 - 2.0.2 differences
>
> Nor does it for me with a delay of 0, but it works OK with a delay of 1 -
> did you try that?
>
> I'll fix the code so it behaves better.
>
> S.
> On Wed, 15 Dec 2004 17:33:12 -0000, Ashley Hayes <[EMAIL PROTECTED]>
> wrote:
> > No the startup delay didn't do the trick
> > Ta,
> > A
> >
> > -----Original Message-----
> > From: sebb [mailto:[EMAIL PROTECTED]
> > Sent: 15 December 2004 17:25
> > To: JMeter Users List
> > Subject: Re: Thread Group Scheduler 2.0.1 - 2.0.2 differences
> >
> > That's unexpected. As far as I can remember, the end time is ignored
> > if the duration is specified, so it should not matter what you put....
> >
> > I obviously need to have a look a the code ...
> >
> > Did setting the startup delay to 0 or 1 work?
> >
> > S
> > On Wed, 15 Dec 2004 16:33:30 -0000, Ashley Hayes
> > <[EMAIL PROTECTED]>
> > wrote:
> > > Thanks sebb/peter.
> > > Tried both your suggestions.
> > > Setting the end time to far in the future (2070/01/01 01:00:00)
> > > seems to work as the test duration kicks in and stops the test
> > >
> > > -----Original Message-----
> > > From: sebb [mailto:[EMAIL PROTECTED]
> > > Sent: 15 December 2004 13:00
> > > To: JMeter Users List; Peter Lin
> > > Subject: Re: Thread Group Scheduler 2.0.1 - 2.0.2 differences
> > >
> > > The startup delay and duration fields are supposed to over-ride the
> > > corresponding times.
> > >
> > > I think there was a fix in 2.0.2 to ensure that the duration was
> > > only taken as starting from when the test actually started; this may
> > > have had a side effect.
> > >
> > > However, your example says to start the test in 1970, run it for
> > > 3600 seconds and then stop.
> > >
> > > Try setting the startup delay to 0 or 1, and see if this fixes
> > > things.
> > >
> > > Perhaps the scheduler needs to be cleverer, and assume that a
> > > start-time that has already passed is actually now.
> > >
> > > S.
> > > On Wed, 15 Dec 2004 07:34:38 -0500, Peter Lin <[EMAIL PROTECTED]>
> > > wrote:
> > > > I think it is because the end time is the same. have you tried
> > > > changing the end time to something different?
> > > >
> > > > peter
> > > >
> > > > On Wed, 15 Dec 2004 10:21:41 -0000, Ashley Hayes
> > > > <[EMAIL PROTECTED]> wrote:
> > > > > I've recently upgraded from Jmeter 2.0.1 to 2.0.2 and am
> > > > > experiencing problems with the scheduler on the tread group
> > > > > element. Each thread is only executing the elements under the
> > > > > tread group for one iteration and then stop, it should execute
> > > > > many iterations over 1 hour ( as in version 2.0.1) . There are
> > > > > no errors in the jmeter log.
> > > > >
> > > > > Is there a problem with my scheduler Config?:
> > > > > The Loop Count is "checked" Forever
> > > > > The Scheduler is "checked"
> > > > > Start Time is the default "1970/01/01 01:00:00"
> > > > > End Time is the default "1970/01/01 01:00:00"
> > > > > Duration (seconds) is ${TestDurationInSeconds} , I've also
> > > > > tried the literal 3600 Startup delay (seconds) is [blank]
> > > > >
> > > > > Thanks for you time,
> > > > > A
> > > > >
> > > > > FYI
> > > > > I'm using Windows XP prof and
> > > > > java version "1.4.1_06"
> > > > > Java(TM) 2 Runtime Environment, Standard Edition (build
> > > > > 1.4.1_06-b01) Java HotSpot(TM) Client VM (build 1.4.1_06-b01,
> > > > > mixed
> > > > > mode)
> > > > >
> > > > > ----------------------------------------------------------------
> > > > > --
> > > > > --
> > > > > -
> > > > > 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]
> > >
> > > --------------------------------------------------------------------
> > > -
> > > 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]
> >
> >
>
> ---------------------------------------------------------------------
> 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]
