Question

I’m trying to setup JMeter in a distributed mode.
I have a server running on an ec2 intance, and I want the master to run on my local computer.
I had to jump through some hopes to get RMI working correctly on the server but was solved with setting the “java.rmi.server.hostname” to the IP of the ec2 instance.

The next (and hopefully last) problem is the server communicating back to the master.

The problem is that because I am doing this from an internal network, the master is sending its local/internal ip address (192.168.1.XXX) when it should be sending back the IP of my external connection (92.XXX.XXX.XXX).

I can see this in the jmeter-server.log:

ERROR – jmeter.samplers.RemoteListenerWrapper: testStarted(host) java.rmi.ConnectException: Connection refused to host: 192.168.1.50; nested exception is:

That host IP is wrong. It should be the 92.XXX.XXX.XX address. I assume this is because in the master logs I see the following:

2012/07/29 20:45:25 INFO – jmeter.JMeter: IP: 192.168.1.50 Name: XXXXXX.local FullName: 192.168.1.50

And this IP is sent to the server during RMI setup.

So I think I have two options:

1. Tell the master to send the external IP
2. Tell the server to connect on the external IP of the master.

But I can’t see where to set these commands.

Any help would be useful.

Answer 1

It looks as though this wont work Distributed JMeter Testing explains the requirements for load testing in a distributed environment. Number 2 and 3 are particular to your use case I believe.

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.
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.