Bug 66237 - Constant Throughput Timer : 0 TPS + shared algorithm + thread lifetime runs all Threads - 1
Summary: Constant Throughput Timer : 0 TPS + shared algorithm + thread lifetime runs a...
Status: NEW
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 5.5
Hardware: PC All
: P2 normal (vote)
Target Milestone: JMETER_5.5
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-24 13:21 UTC by nathan88wise
Modified: 2022-08-24 13:43 UTC (History)
0 users



Attachments
Example file where the bug occurs (2.64 KB, application/xml)
2022-08-24 13:21 UTC, nathan88wise
Details
Showing where Thread issue occurs (52.69 KB, image/png)
2022-08-24 13:23 UTC, nathan88wise
Details
Image showing the issue (54.61 KB, image/png)
2022-08-24 13:43 UTC, nathan88wise
Details

Note You need to log in before you can comment on or make changes to this bug.
Description nathan88wise 2022-08-24 13:21:47 UTC
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.
Comment 1 nathan88wise 2022-08-24 13:23:22 UTC
Created attachment 38374 [details]
Showing where Thread issue occurs
Comment 2 nathan88wise 2022-08-24 13:26:30 UTC
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
Comment 3 nathan88wise 2022-08-24 13:43:08 UTC
Created attachment 38375 [details]
Image showing the issue
Comment 4 The ASF infrastructure team 2022-09-24 20:38:23 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/5696