DO NOT REPLY [Bug 36227] New: - Non-Threadsafe Controller

[bu...@apache.org]

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

           Summary: Non-Threadsafe Controller
           Product: JMeter
           Version: 2.0.3
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Main
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: jmeter@binarytwo.com


I think it'd be nice to have a non-threadsafe controller available. 

What I mean, is being able to group a set of requests so that only one thread at
a time would be able to execute them in sequence.

For example, if I'm scripting an action to reassign a bug and there's a
confirmation page, it's possible that two threads could reassign the bug at the
same time to different people, which would break my final results assertions. If
I had a non-threadsafe controller available, I could put the reassign, confirm,
and verify requests inside it and always get predictable results.

I realize it would mean making other threads wait and could bottleneck a large
test, but I think if a controller like this is used responsibly (ie, to group
very small sets of atomic actions) it could be a great help.

-- 
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