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=11844>. 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=11844 Interleave Controller inside Loop Controller fools loop counter ------- Additional Comments From [EMAIL PROTECTED] 2002-08-22 07:01 ------- This is a comment that does not necessarily mean the bug should be REOPENED. JMeter 1.7.3 (and 1.7, by manually recreating the test plan) produces: HTTP Request 1 (iter 1) HTTP Request 2 (iter 2) HTTP Request 3 (iter 3) HTTP Request 1 (iter 4) HTTP Request 2 (iter 5) >From this behaviour for the submitted test plan, we can say that the Simple Controllers are immaterial to the interleaving produced. The Interleave Controller is interleaving across the three actual requests only. The CVS version of JMeter which updates Interleave Controller on 20 August or so, which defaults to Interleave Controllers to ignore subcontroller blocks ON, produces similar, but NOT identical behaviour. I get: HTTP Request 1 (iter 1) HTTP Request 3 (iter 2) HTTP Request 2 (iter 3) HTTP Request 3 (iter 4) HTTP Request 1 (iter 5) >From this behaviour for the submitted test plan, we can say that the Simple Controllers are *material* to the interleaving produced. The Interleave Controller is interleaving the Simple Controllers themselves AND the requests they contain. When ignore subcontroller blocks is OFF, I get the behaviour proposed at the end of the original bug submission. How to deal with the difference between 1.7.3 and current CVS version with ignore subcontroller blocks ON I leave to the JMeter owner/s. 1.7.3 and 1.7 (after translation) test plans will interleave differently using the CVS version. Thanks for your work. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
