Rakshita BJ wrote:
Thank you for the detailed response Dmitri, I appreciate it,
Could you please answer the below questions,
* Since you said " Master connects to slave(s) on port 1099 in order
to transfer the .jmx test plan and send start test event"
*/Should the port 1099 be open in master and slave machine??
Because the port 1099 is open only in the slave and not in the
master machine.
/*
* Since the slave responds to master on random ports and as all
ports are not open in master,
*/ I have to set specific ports "client.rmi.localport" and 3
more consecutive ports open in the firewall, Should I mention the
ports both in master and slave machine properties file??
/*
* */The error I am facing is it because the master is not able to
establish connection to the slave or the slave is not able to send
a response to master?
/*
* */25ccce35-546b-445a-b55c-34b0dc8bab80.png
/*
/
/Thanks and regards,
Rakshita
On Wed, Jul 12, 2023 at 12:13 AM Dmitri T <[email protected]
<mailto:[email protected]>> wrote:
Rakshita BJ wrote:
> Hello Team,
>
> I am trying to run distributed testing in Jmeter.
>
> * I have the same version of Jmeter as well as Java in master and
> slave machines.
> * I have added the remote host IP address to my jmeter.properties
> file.image.png
> * Before running the tests I make sure to start the
> Jmeter-server.bat in my slave machine and once I start it
this is
> what I see
> image.png
> * Port 1099 is open and the firewall rule on it has been removed.
> * Remote hosts(VM) are run using aws and the port 1099 is open in
> security groups.
>
> I performed all the above steps and am getting the below error,
> *the IT team is saying that since Java RMI assigns random ports
> once it makes a connection to remote hosts using 1099,* they
> cannot apply firewall rules on all ports as they don't know
which
> port is used.
> * Screenshot (105)_LI.jpg
> * I have tried assigning a specific port in
client.server.local port
> in jmeter.properties file but that doesn't seem to work
> either.image.png
>
> Could the team please help me in any steps I am missing out on?
What
> could be the reason I am seeing the above error??
>
> Eagerly waiting for the response.
>
> Thanks and regards,
> Rakshita
By default:
1. Master connects to slave(s) on port 1099 in order to transfer the
.jmx test plan and send start test event
2. Slaves connect to master on random free ports to report back the
test metrics/results and end test events
As per JMeter Documentation
<https://jmeter.apache.org/usermanual/properties_reference.html#remote>:
*server_port*
RMI port to be used by the server (must start rmiregistry with
same port).
*client.rmi.localport*
Parameter that controls the RMI ports used by
RemoteSampleListenerImpl
and RemoteThreadsListenerImpl (The Controller)
Default value is 0, which means *ports are randomly assigned.* If
this
is non-zero, it will be used as the base for local port numbers
for the
client engine. At the moment JMeter will open up to three ports
beginning with the port defined in this property.
So if you want to change the port from 1099 you need to set the
appropriate server_port value in /user.properties/ file on slave(s).
Then you can use *remote_hosts* property to inform master about slave
server ports like *remote_hosts=slave1:1099,slave2:2099,slave3=3099
*
If you want to use static port set client.rmi.localport on master
side
like *client.rmi.localport=50000*.
Make sure that:
1. All server_port values are open on the slave(s) in your operating
system firewall
2. On master *client.rmi.localport* and 3 more ports starting from it
are open in the firewall.
More information: Apache JMeter Properties Customization Guide
<https://www.blazemeter.com/blog/jmeter-properties-customization>
I've repeated what needs to be done 3 times using different wording. If
you don't understand essentials of the networking or English I'm sorry I
cannot help anymore. The error indicates that the master cannot connect
to the slave.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
