search cancel

In a Private Cloud, the JMX script runs successfully on the Agents of one Private Location but fails on the agents of a different Private Location

book

Article ID: 201605

calendar_today

Updated On:

Products

BlazeMeter

Issue/Introduction

The same JMX test is executed on the agents of two different On-Premise Private Locations (OPLs), but fail immediately on the agents of one OPL while running successfully on the agents of a second OPL.  This results in a Boot Summary report while the test is starting up similar to the following:

Cause

A review of the bzt.log file on one of the problematic OPL agents reveals that the connection to the local S3 storage device is being dropped which is preventing the files of the test from being downloaded to the agent and causes the test to end prematurely.  Messages similar to the following are recorded in this log file:

[2020-10-15 21:08:07,692 INFO botocore.vendored.requests.packages.urllib3.connectionpool] Starting new HTTP connection (1): <S3 storage device address>
[2020-10-15 21:08:07,702 DEBUG Engine.s3downloader] objects for download: []
[2020-10-15 21:08:07,703 INFO botocore.vendored.requests.packages.urllib3.connectionpool] Resetting dropped connection: <S3 storage device address>
[2020-10-15 21:08:07,712 DEBUG Engine.s3downloader] objects for download: []
[2020-10-15 21:08:07,713 INFO botocore.vendored.requests.packages.urllib3.connectionpool] Resetting dropped connection: <S3 storage device address>
[2020-10-15 21:08:07,722 DEBUG Engine.s3downloader] objects for download: []

Environment

Release : SAAS

Component : BLAZEMETER PERFORMANCE TESTING

Resolution

The agents in an OPL must meet network requirements identified in the Private Location System Requirements article which includes access to the S3 storage server (which is local for a Private Cloud).