master and slave confidential in the same network segment, in order to do distributed (Jmeter to go with the environment variable, so instead of manually starting server)
Distributed unsuccessful, the solution:
1, master and slave end to end to ping
2, after the ping, telnet ip port (Linux terminal), to see if the port is occupied 1099
3, firewall
4, jmeter the log, if the request is made in the past, but did not return the results to see if the problem segment
The main steps:
master end modification:
1, modify remote_hosts = ip: port: To change the boot Linux machines ip and port
slave-side modification: Generally not need to change anything, but it may have a few questions:
The file modification jmeter.properties
1, if you want to change the port, the modified
2, find the file specified: ssl.disable into true
Problems encountered:
Question 1: Routing Problem
The best script in the bin directory.
Question 2: Linux run JMeter server appears to say "is a loopback address", loopback address in question
Solution:
1, modify the hosts file, 127.0.0.1 127.0.0.1 besttest will replace the ip address of the Linux machine, or 127.0.0.1 besttest this line to the comment (#), under a separate line: ip besttest
/ Sbin / ifconfig --- non-root users to obtain ip address command, ifconfig only the root user can directly use
2, startup, specify an ip address, in the bin directory JMeter, there is a document called: jmeter-server (if Linux is to modify the .sh file), this is xxx.xxx.xxx.xxx into the Linux ip address
Issue 3, jmeter-server start, being given that the system can not find the file specified
java.io.FileNotFoundExpection: rmi_keystore.jks (system find the file specified)
errorlevel = 1
How to solve this problem? ? ?
1 embodiment, the jmeter.properties ssl.disable into the true (not file checksum)
Mode 2, if the slave machine on a Linux machine, run create-rmi-keystore.sh file; if a slave machine in the window, you run the create-rmi-keystore.bat file
After the run, fill out the information on their own
After the run, the bin directory will be more of a rmi_keystore.jks file
This file is copied to the slave machine you want to run, you can not process, is a file check problem
Question 4, a distributed execution, they do not understand stuck, generally less than fried ip, because the cause of multiple network cards
A method, independent of the network card is disabled
Method two, jmeter -Djava.rmi.server.hostname = xxx.xxx.xxx.xxx (ip you want to start ip, not jmeter.server)