ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Configured JMeter Properties are not picked up in JMX script

book

Article ID: 226671

calendar_today

Updated On:

Products

BlazeMeter

Issue/Introduction

After setting the JMeter Properties configuration from the BlazeMeter test, it does not appear to be flowing into the JMX script when the test is executed from BlazeMeter.

Cause

The JMeter Properties syntax was not used in the JMX script to pick up the property/value

Environment

Release : SAAS

Component : BLAZEMETER PERFORMANCE TESTING

Resolution

When using JMeter Properties to parameterize a JMX script used in a BlazeMeter Performance test as specified in the JMeter Properties article, it assumes that the JMX script is configured to use the JMeter property by entering a variable in a JMeter element using syntax similar to the following in order to use the configured property value when the test is executed:

${__P(<property_name>,<value>)}

where:

<property_name> is the name of the property configured in the JMeter Property section on the test configuration page and
<value> is a default initial value assigned if the property does not have a configured value.

For example, to control the number of threads in a Thread Group in the test,:

1.  Disable Users on the Configuration page:


2.  Configure a JMeter property to set the desired number of threads:



3.  Then use the JMeter property in the Thread Group for the JMX script that is uploaded to the BlazeMeter test:

Attachments