Constant Throughput Timer : 0 TPS + shared algorithm + thread lifetime runs all Threads - 1
- Dominant language
- Java
- Stars
- 9.5k
- Forks
- 2.3k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 5
Description
**nathan88wise** ([Bug 66237](https://bz.apache.org/bugzilla//show_bug.cgi?id=66237&redirect=false)):
When I specify 0 for the "Target throughput (in sample per minute)" of a Constant Throughput Timer, use either shared algorithm - "all active threads (shared)" or "all active threads in current thread group (shared)" and have a Thread Lifetime specified - the Thread Group will run with <"Number of Threads" - 1> threads.
When using other algorithms in the Constant Throughput Timer, the test will instead stop as expected. Not sure why the shared algorithms should differ; I'm assuming this is a bug.
Created attachment [Test.jmx](https://apache.github.io/jmeter-bugzilla-attachments/37/66237/38373/Test.jmx): Example file where the bug occurs
Test.jmx
````xml
false
true
false
continue
false
-1
10
1
true
300
true
true
return;
groovy
3
throughput
0.0
0.0
````
Severity: normal
OS: All
Contributor guide
Assessment
This issue has not been assessed yet.