Actually this link has some details about this http://jmeter.apache.org/usermanual/remote-test.html It states that "JMeter/RMI requires a connection from the client to the server. This will use the port you chose, default 1099. JMeter/RMI also requires a reverse connection in order to return sample results from the server to the client. This will use a high-numbered port. This port can be controlled by jmeter property called client.rmi.localport in jmeter.properties."
We can fix the client (controller) port where server (agent) returns sample results by specifying it in client.rmi.localport. But still issue is, agent tries to talk back to the controller with controller's private IP (it was seen in agent log). If Controller and agent are on different networks it is not going to work. So question really is, is there a way to specify public ip of client (controller) which should be used by agent? This way, we can setup some routing rules such that any packets received on public ip/port combination on the firewall can be forwarded to private ip/port combination of the controller. Regards, Yogesh -----Original Message----- From: Yogesh Ketkar [mailto:[email protected]] Sent: Tuesday, January 01, 2013 6:11 PM To: 'JMeter Users List' Subject: RE: Controller and Agent on different networks Thanks David for the response. Does Agent machine open a NEW TCP/UDP connection with the controller? Looking at the behavior seems like Controller is able to contact the agent machine but not other way round. Regards, Yogesh -----Original Message----- From: David Luu [mailto:[email protected]] Sent: Sunday, December 30, 2012 4:49 AM To: JMeter Users List Subject: Re: Controller and Agent on different networks I don't know for sure but would imagine that is possible, provided that the agent on a different network can talk to the controller, and vice versa. If they can communicate with each other, it should work. For a quick check you could try pinging the IPs or scan/telnet the ports on those IPs used by JMeter. Something like that, or otherwise try to run JMeter setup and see if it works. This would also assume you have the needed ports open (from firewall) on each side, and there's a route established between the two networks for communication. Both of these, which you may need to set up. On Fri, Dec 28, 2012 at 6:20 AM, Yogesh Ketkar <[email protected]>wrote: > Hello, > > > > Can we have distributed load testing with JMeter where controller and say > one agent is one network and another agent is in another totally different > network (say second agent machine is in Amazon EC2). There already was a > thread on similar lines > ( > http://mail-archives.apache.org/mod_mbox/jmeter-user/201205.mbox/%3C9624FDB > [email protected]%3E) but > with > no answer. > > > > Regards, Yogesh > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
