Issue in running Distributed runs using Jmeter

**Chandrakumar Sekar** ([Bug 65874](https://bz.apache.org/bugzilla//show_bug.cgi?id=65874&redirect=false)):
Hello Team,

Im raising an issue to seek your support and help in executing a Remote distributed runs using Jmeter. Following are the details of the issue and Test VM's that I currently use for Remote distributed runs.

Test VM details:
Machine OS: Windows 2019 Server edition.
Machine configuration: 4 Core CPU and 16 GB RAM.
These machines are restricted across network interms of Firewall.
All machines are having same IP subnet 10.135.159.*

Tool Details:
Jmeter Version: 5.4.1 with updated log4j version.
Java version: 1.8 on all machines
Placed all scripts and data files on same path as of Master machine

Jmeter Configuration details:
As machines are restricted across network, I have opened Firewall between the machines on port 1099 for the purpose of remote distributed runs. Hence, accordingly the Jmeter properties are updated with below details.

Jmeter.properties updated as follows,
remote_hosts = Machine IP which i planned to use as remote agents (slave)
server.rmi.port=1099
server.rmi.local.port=1099

As machine is blocked with firewall restrictions, opened a port 1099 on machines for remote distributed runs.

Observations:
1. Started Jmeter-server.bat on slaves. it started with no exceptions or errors and on the port 1099 as defined in properties file.
2. Jmx was scheduled to run for 2 mins as a validation for Remote distributed runs.
3. Started a jmx using command file jmeter -n -t "Path of Jmx" -R 10.135.159.1,10.135.159.2
4. received a message on slave Jmeter server window that started test at Timestamp.

As an expected result: the given userload should execute on all slaves and Jmeter metrics should reflect in Grafana Dashbaord as wel. However its showing user count and TPS as not appropriate, i.e. Request per second graph was updating on periodic intervals with request counts, also same is being observed in the aggregate report listener on Jmeter GUI window.

Additionally, at the end of the run observed slave got the finished message after 3 mins from scheduled run time of Jmx file.

could you please review the provided details and advise us on this behaviour what is blocking us in executing a remote distributed runs on above said machines?

Thanks in advance,
Chandrakumar Sekar.

Severity: major
OS: All

Start with the reported jmeter.properties values, jmeter-server.bat startup, and the command used for the remote run. Compare the configured ports and host behavior with the delayed completion and intermittent metrics in the Grafana dashboard and aggregate report. Done means identifying a reproducible configuration or networking cause and documenting the verified resolution.

Written by the indexing model from the issue text.