search cancel

Load Test not terminating gracefully

book

Article ID: 215307

calendar_today

Updated On:

Products

BlazeMeter

Issue/Introduction

BlazeMeter Performance load test appears to get stuck and fails to terminate gracefully.

Cause

jmeter.log on the test is very large (> 20G).  Most likely used up all available diskspace on the cloud engine preventing BlazeMeter from generating and uploading the artifacts zip archives.

Errors similar to the following can be found in the jmeter.log file for each problematic Thread Group:

2021-05-18 09:12:38,544 INFO o.a.j.t.JMeterThread: Thread started: Sample-ThreadStarter 8-1
2021-05-18 09:12:38,544 ERROR o.a.j.t.JMeterThread: Test failed!
java.lang.IllegalArgumentException: Could not read file header line for file sample.csv

Environment

Release : SAAS

Component : BLAZEMETER PERFORMANCE TESTING

Resolution

The JMX script contains multiple Thread Groups.  1 or more of the Thread Groups are configured to use CSV files, but the configured CSV files were not uploaded to the test.  This causes JMeter to log an error every time these thread groups are executed flooding the jmeter.log file with the errors and very quickly growing the size of the log. 

Either correct the JMX script to use the uploaded CSV files, or upload the correct CSV files for the test as documented in the Missing Files section of the Test Works Locally but not on BlazeMeter article.