On 05/03/2008, Tom Fernandes <[EMAIL PROTECTED]> wrote: > Hi, > > On Wednesday, 5. March 2008, sebb wrote: > > On 05/03/2008, Tom Fernandes <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > On Wednesday, 5. March 2008, sebb wrote: > > > > On 05/03/2008, Tom Fernandes <[EMAIL PROTECTED]> wrote: > > > > > Hello, > > > > > > > > > > I'm trying to run jmeter remote. Setup as follows: > > > > > > > > > > run jmeter-server on the remote machine (as it looks it binds > > > > > default to port 1099) > > > > > > > > > > on the node have one line > > > > > > > > > > remote_hosts=127.0.0.1:1099 > > > > > > > > > > ssh port forwarding from 1099 of 127.0.0.1 on local machine to > > > > > 127.0.0.1 on remote machine. The forwarding works (tested via > > > > > portsniffing on the remote machine). > > > > > > > > RMI requires that the client can find the server, and the server can > > > > find the client. > > > > > > > > The client sends a message to the server; this includes its return > > > > address. The server has to be able to contact the client to return any > > > > sample data. > > > > > > > > If either the client or the server thinks its ip address is a "local" > > > > address, then the communication will fail to work fully. > > > > > > > > If possible, please try using client server mode without ssh > > > > forwarding first. > > > > > > Hmm - sounds tricky. Node is in the office (internal IP behind a router) > > > - remote server is in the data center (in the same subnet where the > > > server we want to test is). What would you suggest? I dislike the idea of > > > having the jmeter server run on a public port and would rather not have > > > portforwarding from the office router to the jmeter node. > > > > I just meant to try the client-server set up between the current > > client and another node that is accessible without ssh. Ideally also > > use another client and the server without ssh. > > > > That should show if the individual nodes are working OK, and you can > > then worry about adding the ssh tunneling. > > > > > But if necessary we'll open up things a bit. What what the configuration > > > be like. Is it possible to either bind jmeter-server onto the external > > > interface or do the portforwarding into the lan or would we have to do > > > both? > > > > Sorry, no idea. That's really an RMI/Networks issue; I have little > > knowledge of that. > > > > One alternative might be use JMeter in non-GUI mode on the server via > > ssh from the client. > > > > If you are only running one server that would be equivalent and would > > reduce the network traffic during the test. > > > but then there won't be any option to have the Listeners (statistics) run in > real-time to look at, right?
I forgot to mention this: http://jakarta.apache.org/jmeter/usermanual/component_reference.html#Generate_Summary_Results > would there be a way to log them and take a look at them later? > The JTL file can be copied to the client after the run and loaded into any Listener you want. > thanks lots so far :), > > > > Tom > > > --------------------------------------------------------------------- > 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]
