• Embed Doc
  • Copy Link
  • Readcast
  • Collections
  • CommentGo Back
Download
 
JMeter - User's Manual: Remote (Distributed) Testingfile:///C:/Documents%20and%20Settings/olivier/Bureau/jakarta-jmeter...1 sur 311/09/2006 11:32
Index Next Prev
15. Remote Testing
In the event that your JMeter client machine is unable, performance-wise, to simulate enoughusers to stress your server, an option exists to control multiple, remote JMeter engines from asingle JMeter GUI client. By running JMeter remotely, you can replicate a test across manylow-end computers and thus simulate a larger load on the server. One instance of the JMeter GUI client can control any number of remote JMeter instances, and collect all the data fromthem. This offers the following features:Saving of test samples to a local machineManagment of multiple JMeterEngines from a single machine Note that while you can indeed execute the JMeterEngine on your application server, youneed to be mindful of the fact that this will be adding processing overhead on the applicationserver and thus your testing results will be somewhat tainted. The recommended approach isto have one or more machines on the same Ethernet segment as your application server thatyou configure to run the JMeter Engine. This will minimize the impact of the network on thetest results without impacting the performance of the application serer itself.
Step 1: Start the servers
To run JMeter in remote node, start the JMeter server component on all machines you wish torun on by running the
JMETER_HOME/bin/jmeter-server
(unix) or 
JMETER_HOME/bin/jmeter-server.bat
(windows) script.
Step 2: Add the server IP to your client's Properties File
Edit the properties file
on the controlling JMeter machine
. In /bin/jmeter.properties, find the property named, "remote_hosts", and add the value of your running JMeter server's IP address.Multiple such servers can be added, comma-delimited. Note that you can also use the -Jcommand line optionto specify the remote host(s) to use.E.g. jmeter -Jremote_hosts=host1,127.0.0.1,host2
Step 3: Start the JMeter Client
 Now you are ready to start the controlling JMeter client. For MS-Windows, start the clientwith the script "bin/jmeter.bat". For UNIX, use the script "bin/jmeter". You will notice that theRun menu contains two new sub-menus: "Remote Start" and "Remote Stop" (see figure 1).These menus contain the client that you set in the properties file. Use the remote start and stopinstead of the normal JMeter start and stop menu items.
 
JMeter - User's Manual: Remote (Distributed) Testingfile:///C:/Documents%20and%20Settings/olivier/Bureau/jakarta-jmeter...2 sur 311/09/2006 11:32
Figure 1 - Run Menu
15.1 Doing it Manually
In some cases, the jmeter-server script may not work for you (if you are using anOS platform not anticipated by the JMeter developers). Here is how to start theJMeter servers (step 1 above) with a more manual process:
Step 1a: Start the RMI Registry
JMeter uses Remote Method Invocation (RMI) as the remote communicationmechanism. Therefore, you need to run the RMI Registry application (which isnamed, "rmiregistry") that comes with the JDK and is located in the "bin"directory. Before running rmiregistry, make sure that the following jars are inyour system claspath:JMETER_HOME/lib/ext/ApacheJMeter_core.jar JMETER_HOME/lib/jorphan.jar JMETER_HOME/lib/logkit-1.2.jar The rmiregistry application needs access to certain JMeter classes. Runrmiregistry with no parameters. By default the application listens to port 1099.
Step 1b: Start the JMeter Server
Once the RMI Registry application is running, start the JMeter Server. Use the"-s" option with the jmeter startup script ("jmeter -s").Steps 2 and 3 remain the same.
15.2 Tips
If you're running Suse Linux, these tips may help. The default installation mayenable the firewall. In that case, remote testing will not work properly. Thefollowing tips were contributed by Sergey Ten.If you see connections refused, turn on debugging by passing the followingoptions.The solution to the problem is to remove the loopbacks 127.0.0.1 and 127.0.0.2from etc/hosts. What happens is jmeter-server can't connect to rmiregistry if 127.0.0.2 loopback is not available. Use the following settings to fix the problem.Replace`dirname $0`/jmeter -s "$@"WithHOST="-Djava.rmi.server.hostname=[computer_name][computer_domain]-Djava.security.policy=`dirname $0`/[policy_file]"`dirname $0`/jmeter $HOST -s "$@"Also create a policy file and add [computer_name][computer_domain] line to/etc/hosts.
of 00

Leave a Comment

You must be to leave a comment.
Submit
Characters: ...
You must be to leave a comment.
Submit
Characters: ...