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=40229>. 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=40229 Summary: Nested IfControllers failing on 2nd run Product: JMeter Version: 2.2 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Main AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] If a ThreadGroup that is set to run more than once is created with nested IfControllers like this: Thread Group | +-IfController 1, (condition A) | | | +-Sampler 1 | | | +-IfController 2, (condition B) | | | +-Sampler 2 | ... the Sampler 2 will not be run on the second pass despite the fact that the conditions in both IfControllers pass. On the third pass, it will be executed properly. After stepping through the code, I verified that resetCurrent() on the nested IfController is not executed between the first and second passes. However, it is executed during the second pass. This explains why it runs properly on the third pass. A simple workaround exists, (but it is not necessarily intuitive): the nested IfController is pulled out to the main level of execution and its condition is modified to be the logical composite of the original top and nested IfController. Thread Group | +-IfController 1, (condition A) | | | +-Sampler 1 | |-IfController 2, (condition A && condition B) | | | +-Sampler 2 | ... Hope that helps the next user with this problem until the bug is fixed! -- 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]
