Skip to content

fix: allow usage of variables in ConstantThroughputTimer.throughput and PreciseThroughputTimer - #6192

Merged
vlsi merged 1 commit into
apache:masterfrom
vlsi:timer_init
Dec 18, 2023
Merged

vlsi merged 1 commit into
apache:masterfrom
vlsi:timer_init

Conversation

@vlsi

@vlsi vlsi commented Dec 18, 2023

Copy link
Copy Markdown
Collaborator

Previously, the timers might fail initialization in case variable was not present when test started.

The current workaround is to avoid implementing TestStateListener in the timers so JMeter does not attempt evaluating all the properties before test starts.

fixes #6165

…nd PreciseThroughputTimer

Previously, the timers might fail initialization in case variable was not present
when test started.

The current workaround is to avoid implementing TestStateListener in the timers
so JMeter does not attempt evaluating all the properties before test starts.

fixes apache#6165
@vlsi vlsi added this to the 5.6.3 milestone Dec 18, 2023
@vlsi
vlsi merged commit 9b250b6 into apache:master Dec 18, 2023
@vlsi
vlsi deleted the timer_init branch December 27, 2023 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The Constant Throughput Timer is throwing a NullPointerException when using variables (vars.get) in "Target Throughput"-field

1 participant