#USING TUNNELLING WITH APACHE JMETER ZIP FILE#

To test your setup, start the “jmeter-server” application on one of the slaves. This covers the work you need to do on the slaves.

Save the file and while still being root, restart iptables with.

A RH-Firewall-1-INPUT -p tcp -m tcp -dport 50000 -j ACCEPT A RH-Firewall-1-INPUT -p udp -m udp -dport 50000 -j ACCEPT A RH-Firewall-1-INPUT -p tcp -m tcp -dport 1099 -j ACCEPT A RH-Firewall-1-INPUT -p udp -m udp -dport 1099 -j ACCEPT As “root” user, edit the iptables configuration in /etc/sysconfig/iptables and add the following lines, just above the first “REJECT” line (the order is important here):.Save the jmeter.properties file and copy it over to all the other machines (in the correct location).On the first machine, edit the jmeter.properties file in the /bin folder of the unpacked jMeter installation and uncomment the line containing the setting.At the time of this writing I am using jMeter 2.6. Make sure that the files in the bin directory are executable with

#USING TUNNELLING WITH APACHE JMETER ZIP FILE#

Download jmeter as a zip file and unzip it on each of the jMeter slave machines.Create a “jmeter” user on each of the machines so that you don’t have to run the jMeter process as a root user. In most jMeter setups, the slaves are Linux machines (any flavor will do, mine are redhat). If your setup looks like the one above, or if your setup involves having your jMeter master machine on a different subnet and/or behind a firewall, here’s what you need to do. All the information can be found, but it took me quite some time to piece it all together. Getting this all to behave nicely wasn’t trivial. It took some fiddling with iptables, the jMeter configuration and ssh tunneling to get it to work.

Normally that is no problem, but jMeter has this funny construction where the slave (jMeter server) wants to connect back to the master (jMeter gui). In my case, I had to test an application which was inside our corporate network, while working from home through a VPN and a firewall. I thought it would be straight forward but I ran into some interesting things you might want to know if you are considering distributed testing using jMeter. This week I created a jMeter test setup for distributed testing.

Using tunnelling with apache jmeter