A Network problem encountered in JMeter distributed pressure Measurement
Note: this problem should not only be caused by distributed stress testing, but also a common network problem, which has nothing to do with distributed pressure testing.
Summary of network problems, here is another one: https://blog.51cto.com/11009785/2400395
Operating environment: home network
The computer is windows 8.1.It is connected to the wifi of your own home. It is not plugged into the network cable as a master computer.
The virtual machine is installed on the computer using VMware Workstation, and the centos6.5 installed by the virtual machine is used as a slave machine, and the network is bridged.
The network problems encountered are as follows:
The slave machine is centos. Run jmeter-server and start up normally.
The master computer is a windows machine, aggregating the report, but the running result has not been received.
Troubleshooting:
Go to the slave machine, go to the jmeter\ bin directory, vi jmeter-server.log
The above error report means that the windows master cannot be connected and the ip address of the connection is given.
Go to windows Mastercomputer, run-- > cmd-- > ipconfig, find the ip address, and check the name of its corresponding network card.
For example, it's one of the three names in the picture below.
Then, find it in the windows master network connection according to the corresponding name, as shown in the following figure
After finding the corresponding network card here, right-click-- > disable
Go to the slave machine and rerun (must rerun) jmeter-server
Go to the Mastercomputer, reopen jmeter (must be reopened), load the script, run-- > start the slave machine remotely, and perform the stress test again
View the aggregate report and receive the result information, as shown in the following figure
For example, on my computer, every time I configure remote_hosts in the jmeter.properties file of my Mastercomputer, there will be a local connection.
And then this problem happened.
I disable this first every time, then restart to test it, and then ok it.
