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

           Summary: RunOnce inside Runtime-Controller runs more than once
           Product: JMeter
           Version: Nightly (Please specify date)
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Main
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


Below is a fragment of our jmeter test tree used for functional testing of a 
webapp:

thread group
 |
 +- Runtime controller
     |
     +- Run once controller
         |
         +- Http request sampler
         |
         +- While Controller
         |
         .. more stuff here


The controllers below the RunOnce controller take some time to execute, around 
60 seconds. The while controller basically polls a status page to check the 
progress of some work unit triggered earlier in the test.

There are some special cases in which such progress may not happen and the test 
should fail. The easiest way for us to deceide if a test should fail would be a 
timeout. If that timeout is reached and the status page still does not contain 
a certain message, the test should fail.

Therefore I set the timeout in the Runtime controller, 120 seconds for example. 
The RunOnce controller was intended to ensure that the subtree below it is 
actually executed only once which is very important for a test scenario. 

While checking the result tree I can see one of two behaviours. With a small 
timeout, the runtime controller will stop executing the subtree after the given 
runtime is over. That's fine. If the timeout is set to a larger value jmeter 
behaves different. After the first iteration, if there is runtime left, jmeter 
will just re-execute the tree below the runonce controller. 

Did I mis-understood the documentation of the run-once controller or is this a 
bug? 

Beside that - is there a better way to set a maximum execution time on a test 
tree fragment?

(I'm using the nightly build 20050118)

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to