Bug 36227 - Non-Threadsafe Controller
Summary: Non-Threadsafe Controller
Status: RESOLVED DUPLICATE of bug 43384
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.0.3
Hardware: All All
: P2 enhancement with 1 vote (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-17 16:23 UTC by Peter Bernier
Modified: 2009-05-08 17:54 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Bernier 2005-08-17 16:23:10 UTC
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.
Comment 1 Sebb 2007-12-05 17:28:08 UTC
See also Bug 43384
Comment 2 Sebb 2009-05-08 17:54:39 UTC
This functionality could be addressed by bug 43384

*** This bug has been marked as a duplicate of bug 43384 ***
Comment 3 The ASF infrastructure team 2022-09-24 20:37:35 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1581