When using Jmeter to implement distributed stress testing, when 1. the windows scheduler can be connected to the linux load machine (which can also be executed remotely), but no results are returned; 2. the windows scheduler gets stuck when calling the Linux load machine. You can try the following steps to solve
Option 1: Enter the bin directory of jmeter, hold down shift and click the right mouse button to open the window here
Execute jmeter -Djava.rmi.server.hostname=192.168.1.182 (change to ip on windows)
Option 2: Modify the jmeter.bat startup file
Find jmeter.bat in the bin directory and edit it
If Jmeter4.0 has not been modified, the default is the configuration in the picture
change to
code show as below:
set rmi_host=-Djava.rmi.server.hostname=192.168.1.182 (change to your own IP)
set ARGS=%JAVA9_OPTS% %DUMP% %HEAP% %VERBOSE_GC% %GC_ALGO% %DDRAW% %SYSTEM_PROPS% %JMETER_LANGUAGE% %RUN_IN_DOCKER% %rmi_host%
Done, let's see the principle
This usually occurs when there are multiple network cards in the computer.
When the jmeter of the Windows scheduler was started, the ip of the network card we needed was not used, and the load machine could not find the scheduler, so various problems appeared.