-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JMeter 5.6 - ThreadGroups are running endlessly in non-gui mode #6008
Comments
The default value is indeed not saved. |
…itializing in the constructor Previously LoopController initialized continue_forever=true in the constructor, however, and ThreadGroup.setMainController flipped the value to false. It caused inconsistency since non-GUI launch does not call ThreadGroup.setMainController. Using default=true enables to treat "false" as non-standard, so =false is saved t the jmx, and it gets loaded in non-GUI as well. Fixes apache#6008
…itializing in the constructor Previously LoopController initialized continue_forever=true in the constructor, however, and ThreadGroup.setMainController flipped the value to false. It caused inconsistency since non-GUI launch does not call ThreadGroup.setMainController. Using default=true enables to treat "false" as non-standard, so =false is saved t the jmx, and it gets loaded in non-GUI as well. Fixes apache#6008
Should consider a hotfix such as a quick 5.6.1 version release.
Thank you
SG
…________________________________
From: Vladimir Sitnikov ***@***.***>
Sent: Monday, June 26, 2023 16:52
To: apache/jmeter ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [apache/jmeter] JMeter 5.6 - ThreadGroups are running endlessly in non-gui mode (Issue #6008)
Since JMeter 5.6 the ThreadGroups without a specified Thread lifetime run endlessly.
Also the property in the JMX beneath the ThreadGroup is missing
The default value is indeed not saved.
However, it should be loaded as "default".
—
Reply to this email directly, view it on GitHub<#6008 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAXQDSUBLJ2P3M6ZFPROKGTXNGHZ5ANCNFSM6AAAAAAZUD7BJ4>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
…itializing in the constructor Previously LoopController initialized continue_forever=true in the constructor, however, and ThreadGroup.setMainController flipped the value to false. It caused inconsistency since non-GUI launch does not call ThreadGroup.setMainController. Using default=true enables to treat "false" as non-standard, so =false is saved t the jmx, and it gets loaded in non-GUI as well. Fixes apache#6008
…itializing in the constructor Previously LoopController initialized continue_forever=true in the constructor, however, and ThreadGroup.setMainController flipped the value to false. It caused inconsistency since non-GUI launch does not call ThreadGroup.setMainController. Using default=true enables to treat "false" as non-standard, so =false is saved t the jmx, and it gets loaded in non-GUI as well. Fixes #6008
Is there a workaround to this issue before 5.6.1 comes out? Such as setting a value to the LoopController attribute to make it stop after executing the tests just like it does in UI mode? |
The workaround is to edit Unfortunately, it will disappear every time you save the file in JMeter 5.6. An alternative option is to use a different thread group. For instance, Open Model Thread Group. |
Thank you, that will do the trick for us. We store the jmx file in GitHub, so we can add this manually to make the automated tests (that run in non-UI mode) work again until 5.6.1 is out! Thanks! |
5.6.1 is released, enjoy |
Expected behavior
In gui mode, JMeter acts as always.
In non-gui mode JMeter runs all Thread Groups endlessly, when there is no specified Thread lifetime.
JMeter was used to run the number of configured Loops - even without a specified Thread lifetime.
Also there was a Property in the JMX beneath the ThreadGroup
Actual behavior
Since JMeter 5.6 the ThreadGroups without a specified Thread lifetime run endlessly.
Also the property in the JMX beneath the ThreadGroup is missing
Steps to reproduce the problem
Open a TestPlan from JMeter 5.5 with JMeter 5.6, save it and review the difference.
Otherwise use this test plan non-stopping-threads-jmeter-5.6.jmx.txt
run in gui mode -> should execute...
.. the setUp Thread Group once
..the Thread Group 4 times
<path-to-jmeter-5.6>\jmeter.bat -t non-stopping-threads-jmeter-5.6.jmx -l jmeter.log -n
JMeter Version
5.6
Java Version
openjdk version "17.0.7" 2023-04-18 LTS OpenJDK Runtime Environment (build 17.0.7+7-LTS) OpenJDK 64-Bit Server VM (build 17.0.7+7-LTS, mixed mode, sharing)
OS Version
Microsoft Windows [Version 10.0.19045.3086]
The text was updated successfully, but these errors were encountered: