Actually,
I just noticed that Amazon EC2 servers are all on the same subnet
together.
James McBryan
On Aug 19, 2009, at 1:59 PM, James McBryan wrote:
Hey Claude,
In your article, you mention "The first problem I faced is that the
JMeter master and its slaves must be in the same sub-network to be
able to communicate, so my JMeter farm had to define two different
roles, one for the master (jmeter-master) with only one instance
and one for the slaves (jmeter-slave) with as many instances as
necessary."
How did you get each of the AMI instances on to the same sub-
network. I am not using anything like scalr, is there anyway
without scalr to create like 3 AMI instances on the same subnetwork?
James McBryan
On Aug 18, 2009, at 3:18 AM, Claude Vedovini wrote:
Hi James,
I ran into the same issue, the master and slaves need to be on the
same sub-network.
I wrote a blog post explaining my setup:
http://vedovini.net/2009/08/jmeter-distributed-testing-with-amazon-
ec2/
Claude Vedovini
---
Software Consulting & Development
+41 78 617 86 98
http://vedovini.net/
http://www.dita-op.org/
2009/8/18 James McBryan <[email protected]>:
Hey JMeter Users,
I am trying to use JMeter with this setup:
1) Server on Amazon EC2 with its own static IP aaa.bbb.ccc.ddd
2) Client on my local dev box behind a router with an IP address if
192.168.0.10
To run the server I execute
./bin/jmeter_server
To run the client I type
./bin/jmeter -n -t bin/testplan.jmx -R aaa.bbb.ccc.ddd
When I run the test plan the server hangs and the tests never
finish and the
results never populate. Looking at the jmeter-server.log I see Java
exceptions like this:
2009/08/17 20:49:25 INFO -
jmeter.samplers.RemoteListenerWrapper: Test
Started on aaa.bbb.ccc.ddd
2009/08/17 20:52:34 ERROR - jmeter.samplers.RemoteListenerWrapper:
testStarted(host) java.rmi.ConnectException: Connection refused
to host:
192.168.0.10; nested exception is:
java.net.ConnectException: Connection timed out
And looking at nmap, my server is sending these every minute or so:
22:35:36.106299 IP aaa.bbb.ccc.ddd.42641 > 192.168.0.10.58349: S
1916790738:1916790738(0) win 5840 <mss 1460,sackOK,timestamp
90441062
0,nop,wscale 7>
I can understand why the client test doesn't work.. the remote
server is
sending packets to the wronge place. I have looked through
numerous mailing
posts and it seems like many other people have these problems
however no one
really reports a succesful solution. I have concluded that
JMeter just
won't work from clients with private IP addresses. Is this
true? and if
not (hopefully not) what is the solution?
Thanks,
James
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
