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.

bzt Execution of JMeter Script in Cloud Never Ends

book

Article ID: 199044

calendar_today

Updated On:

Products

BlazeMeter

Issue/Introduction

The execution of a simple jmeter script using "bzt script.jmx -cloud" never ends in spite of the fact that the script duration is set (within the script) to 5 minutes.

Cause

JMX scripts executed directly from a local bzt call uses the account defaults for the JMX load configuration in the cloud.  That means 1 VU and the account max duration is applied to the test.

Environment

Release :

Component : BLAZEMETER PERFORMANCE TESTING

Resolution

To control the JMX script load kicked off locally from the bzt command and executed in the cloud, it is necessary to configure the load and specify the JMX script to execute from a YML file executed from bzt.  For example, to execute the sample.jmx script with 1 VU, a 10 second Ramp Up time, and Duration of 5 minutes, create a sample.yml file with the following contents:

execution:
  concurrency: 1
  hold-for: 5m
  ramp-up: 10s
  scenario: sample

scenarios:
  sample:
    script: sample.jmx

Then to run the JXM test in the cloud execute the following command:

bzt sample.yml -cloud