You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2004/10/08 08:35:59 UTC

DO NOT REPLY [Bug 31596] New: - Duration does not work correctly when using Scheduler and start Time

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31596>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31596

Duration does not work correctly when using Scheduler and start Time

           Summary: Duration does not work correctly when using Scheduler
                    and start Time
           Product: JMeter
           Version: 2.0.1
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Main
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: andrew.r.bredhauer@transport.qld.gov.au


When using the Scheduler to start a test at a point in time in the future the 
duration setting does not appear to work correctly. 
In our specific case we had a duration of 1 hour (3600 seconds) and a start 
time of 17:00:00. We started JMeter sometime between 16:30 and 16:45. At 
around 17:45 the test began to shut down. From this behaviour my assumption is 
that the duration value commences couting down when JMeter is started not when 
the actual test is started. 
In an extreme example a test executed a single sampler and then stopped as the 
duration had elapsed before the start time was reached. 
This sounds like a bug to me but the documentation is not clear in regard to 
exactly how the duration value is interpreted. Can someone tell me if this is 
the desired behaviour or not so we can adjust our testing appropriately.

Thanks

Andrew

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org


Re: DO NOT REPLY [Bug 31596] New: - Duration does not work correctly when using Scheduler and start Time

Posted by sebb <se...@gmail.com>.
The behaviour you describe is not the intention, i.e. it is a bug.

I think this may have been fixed after 2.0.1 was released, in which
case there is a nightly you might like to try - no guarantees!

S.

On 8 Oct 2004 06:35:59 -0000, bugzilla@apache.org <bu...@apache.org> wrote:
> DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
> RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
> <http://issues.apache.org/bugzilla/show_bug.cgi?id=31596>.
> ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
> INSERTED IN THE BUG DATABASE.
> 
> http://issues.apache.org/bugzilla/show_bug.cgi?id=31596
> 
> Duration does not work correctly when using Scheduler and start Time
> 
>            Summary: Duration does not work correctly when using Scheduler
>                     and start Time
>            Product: JMeter
>            Version: 2.0.1
>           Platform: PC
>         OS/Version: Windows XP
>             Status: NEW
>           Severity: Normal
>           Priority: Other
>          Component: Main
>         AssignedTo: jmeter-dev@jakarta.apache.org
>         ReportedBy: andrew.r.bredhauer@transport.qld.gov.au
> 
> When using the Scheduler to start a test at a point in time in the future the
> duration setting does not appear to work correctly.
> In our specific case we had a duration of 1 hour (3600 seconds) and a start
> time of 17:00:00. We started JMeter sometime between 16:30 and 16:45. At
> around 17:45 the test began to shut down. From this behaviour my assumption is
> that the duration value commences couting down when JMeter is started not when
> the actual test is started.
> In an extreme example a test executed a single sampler and then stopped as the
> duration had elapsed before the start time was reached.
> This sounds like a bug to me but the documentation is not clear in regard to
> exactly how the duration value is interpreted. Can someone tell me if this is
> the desired behaviour or not so we can adjust our testing appropriately.
> 
> Thanks
> 
> Andrew
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org