Bug 40961 - Maintain constant number of clients after assertion failure
Summary: Maintain constant number of clients after assertion failure
Status: RESOLVED DUPLICATE of bug 30563
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: unspecified
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-13 11:40 UTC by Paul Kuykendall
Modified: 2011-11-12 15:37 UTC (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Kuykendall 2006-11-13 11:40:49 UTC 
It would be useful to have the ability to set a maximum number of threads
(users) for a thread group such that when a thread group is configured to "Stop
Thread" on an assertion failure the currently executing thread will stop, but
JMeter will start a replacement thread.  This would allow for easier exception
handling during test plan creation.

Using the "Continue" action doesn't seem to fit this application as eventually
all of the threads will fail, ending the test.
Comment 1 Sebb 2006-11-14 05:56:27 UTC 
One way to do this - in the GUI - would be to add a "Restart Thread" option.

This would allow for more flexibility than making the change only at the Thread 
Group level.
Comment 2 Philippe Mouawad 2011-11-12 15:37:52 UTC 
Start Next loop fixes this request

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