Issue
A test stop soon after it is initiated in JMeter.
Possible cause 1
The most likely cause is that Loop Controller is used in the JMeter testing plan and the Loop Count parameter is set to 1.
Solution
We recommend that you do not configure the Loop Count parameter. We recommend that you set the number of loops in the load configuration. For more information, see Configure load models and levels.
Possible cause 2
A normal thread group for stress testing is set to Set Up ThreadGroup by mistake. As a result, stress testing is executed only once at script startup, after which the concurrency drops to zero.
Solution
Set the thread group for stress testing to ThreadGroup.