Thanks for the answer. =)
All mentioned sources I used to make my «research» ;) But in BlazeMeter docs
there are transperent network (without NAT) sugested and docs on parameters on
jmeter.apache.org are not very strieght. We have two hosts and two roles for
each. So it is four combinations. And the docs are not so clear which port in
which case and who uses.
Check it out! for the server_port and server.rmi.port it is written 1099 to be
default. There are statements: «used by the server» and «used to access the
server» now I can guess, that «used by» means «local» and «used to access»
means remote. But still confusing. We specify «remote» port in «remote_hosts».
So «server.rmi.port» overrides 1099 in case if I dont specify port in
«remote_hosts»? confusing… to understand. In addition I saw non-referenced
behavior but I may be mistaken, I had some issues with versions at start.
Also for me it was not abvious that the port to connect to I declare on the
accepting host.
I know its my fault, the message is too long to read =) I tryed to cover all
blank spaces.
Offcourse I use netstat and wireshark!
I do NAT port farwarding on the remote-slave-server machine for ports 1099 and
(in my case 4000)
My question about the ports is that controller-master-client firewalld is
blocking incoming connections on opened ports NNNN++1 (client.rmi.localport).
And It is not behind a NAT. I suppose that it is because ports are higher then
1000… but I am not sure.
PS Not three but two ports NNNN+1 and NNNN+2 are actualy were used.
>Суббота, 3 апреля 2021, 12:07 +03:00 от [email protected] <[email protected]>:
>
>As per Remote hosts and RMI configuration
>< https://jmeter.apache.org/usermanual/properties_reference.html#remote >
>
>
>> 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.
>*
>> You may need to open corresponding ports in the firewall on the Controller
>> machine.
>*
>>
>
>So I would recommend checking which ports are being used by JMeter using
>i.e. netstat < https://en.wikipedia.org/wiki/Netstat > tool and open them
>in the firewall.
>
>You will also need to configure the port forwarding
>< https://en.wikipedia.org/wiki/Port_forwarding > on NAT level otherwise the
>master won't be able to "see" the slave.
>
>An example of master-slave network configuration can be found in the JMeter
>Distributed Testing with Docker
>< https://www.blazemeter.com/blog/jmeter-distributed-testing-with-docker >
>article.
>
>
>
>
>
>--
>Sent from: http://www.jmeter-archive.org/JMeter-User-f512775.html
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]
--
Aki Shidary
