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 2005/05/04 15:04:00 UTC

DO NOT REPLY [Bug 34739] New: - Constant throughput timer errorneous computation of delays in non legacy mode

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=34739>.
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=34739

           Summary: Constant throughput timer errorneous computation of
                    delays in non legacy mode
           Product: JMeter
           Version: 2.0.3
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Main
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: iulargsb@yahoo.com


If you have more than one thread group with a constant througput timer in each
of them set in non legacy mode, then the actual throughput of each thread group
is false computed. The computations are made using
JMeterContextService.getNumberOfThreads(), but this method returns the total
number of threads from all thread groups. The computations should be made using
the number of threads from the current thread group.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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