JMeter Distributed Testing Step-by-step
This short tutorial explains how to use multiple systems to perform stress testing. Before we start,
there are a couple of things to check.
1. the firewalls on the systems are turned off.
2. all the clients are on the same subnet.
3. the server is in the same subnet, if 192.x.x.x or 10.x.x.x ip addresses are used. If the server
doesn't use 192 or 10 ip address, there shouldn't be any problems.
4. Make sure JMeter can access the server.
5. Make sure you use the same version of JMeter on all the systems. Mixing versions may not work correctly.
Once you've made sure the systems are ready, it's time to setup remote testing. The tutorial
assumes you already have JMeter installed on all the systems.
The way JMeter works is 1 master
controller initiates the test on multiple slave systems.
Before we dive into the step-by-step instructions, it's a good idea to define the terms and make sure
the definition is clear.
Master – the system running Jmeter GUI, which controls the test
Slave – the system running jmeter-server, which takes commands from the GUI and send requests to
the target system(s)
Target – the webserver we plan to stress test
1. On the slave systems, go to jmeter/bin directory and execute jmeter-server.bat (jmeter-server on
unix). On windows, you should see a dos window appear with “jre\[version]\bin\rmiregistry.exe”.
If this doesn't happen, it means either the environment settings are not right, or there are
multiple JRE installed on the system. Note: [version] would be the jre version installed on the system.
1. Open jmeter-server.bat in a text editor
2. go to line 44 and find “:setCP”
3. edit “START rmiregistry” to the full path. Example: “START
2. On master system acting as the console, open windows explorer and go to jmeter/bin directory
3. open jmeter.properties in a text editor
4. edit the line “remote_hosts=127.0.0.1”
5. add the IP address. For example, if I have jmeter server running on 192.168.0.10, 11, 12, 13, and
14, the entry would like like this:
6. Start jmeter.
7. Open the test plan you want to use 2/4 Starting the Test
At this point, you are ready to start load testing. If you want to double check the slave systems are
working, open jmeter.log in notepad.
You should see the following in the log.
Jmeter.engine.RemoteJMeterEngineImpl: Starting backing engine
If you do not see this message, it means jmeter-server did not start correctly. For tips on debugging
the issue, go to the tips section. There are two ways to initiate the test: a single system and all
Start a single clients
1. click Run at the top
2. select Remote start
3. select the IP address
Start all clients
... to read more articles, visit http://sqa.fyicenter.com/art/