| Summary: | Constant Throughput Timer : 0 TPS + shared algorithm + thread lifetime runs all Threads - 1 | ||
|---|---|---|---|
| Product: | JMeter - Now in Github | Reporter: | nathan88wise |
| Component: | Main | Assignee: | JMeter issues mailing list <issues> |
| Status: | NEW --- | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | 5.5 | ||
| Target Milestone: | JMETER_5.5 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Attachments: |
Example file where the bug occurs
Showing where Thread issue occurs Image showing the issue |
||
Created attachment 38374 [details]
Showing where Thread issue occurs
Also - just a few clarifications: - This happens with other samplers. I tried with a JMS publisher and a Dummy Sampler (plugin) - It still occurs when Loop Count isn't set to infinite. Seems to be as long as a Thread duration is provided Created attachment 38375 [details]
Image showing the issue
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/5696 |
Created attachment 38373 [details] Example file where the bug occurs 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.