DO NOT REPLY [Bug 15318] New: - Ramp-up not controlling start of thread

[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=15318>.
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=15318

Ramp-up not controlling start of thread

           Summary: Ramp-up not controlling start of thread
           Product: JMeter
           Version: 1.7.3
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Main
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: jstrachman@athenium.com


My understanding is that the ramp-up function is supposed to control in what 
order the threads get launched.  For some reason, even when I use large values 
for the ramp-up, it still often starts them in seemingly random order, e.g. 
Thread 1, then 3, then 2 will start.  This screws up things like HTML Parameter 
Mask objects.  (I would imagine that Counters also will suffer the same problem 
but I can't use 1.8 due to some silly bug.)

Here's an example of the output:

Running the test!
 (The system cannot find the path specified)
 (The system cannot find the path specified)
Thread PFRClassicMode-1 started
Thread PFRClassicMode-2 started
Thread PFRClassicMode-4 started
Thread PFRClassicMode-3 started
Thread PFRClassicMode-5 started
Thread PFRClassicMode-6 started
Thread PFRClassicMode-7 started
Thread PFRClassicMode-8 started
Thread PFRClassicMode-9 started
Thread PFRClassicMode-10 started

There's a 15 second ramp-up, so I can't figure out why thread 4 starts before 
thread 3, and my userIDs get all screwed up.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>