DO NOT REPLY [Bug 17688] New: - ConstantThroughputTimer does not work in non-GUI (batch) mode

[bu...@apache.org]

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

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17688

ConstantThroughputTimer does not work in non-GUI (batch) mode

           Summary: ConstantThroughputTimer does not work in non-GUI (batch)
                    mode
           Product: JMeter
           Version: 1.8.1
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Main
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: jkb@stian.freeserve.co.uk


ConstantThroughputTimer does not work in non-GUI (batch) mode.
This is because the "delay" field does not get set up - it remains as zero.

==

The similar ConstantTimer works OK in non-GUI mode.
It uses iterationStarted() to set the delay from the relevant properties 
string, which seems to be set up from the JMX record in non-GUI mode.

However, iterationStarted() seems to be called every time through the loop, so 
maybe setJMeterVariables() would be a better place to calculate the delay and 
save it ... hope to find time to test this soon; will post details later.

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