Hi Felix, You're right. It is too chary that to mask the internal IP address.
I am not sure about what kind Jmeter server listening ports you mentioned. In my case, the listening port of Jmeter server is 4000 and RMI registry server is 1099. Do you mean I should pay more attention to additional high numbered ports besides listening ports of Jmeter server and RMI registry server? I also find that with or without tunnel to port 4000, I both got same error message "NoRouteToHostException". So I guess, even though the client communicates RMI server via tunnel, it will try to reach Jmeter server by host's IP address directly. Best regards, Flik On 7/20/10 6:58 PM, "Felix Frank" <[email protected]> wrote: Hi, first off, you need not anonymize internal IP adresses, I guess ;-) I found it necessary in a similar context to be aware which ports are actually opened by the Jmeter server, experience suggests that yet another, quite high numbered random port is also opened. In Linux, use netstat -tlnp to find out where Java is listening. Forward the appropriate ports and it Should Work. HTH Felix On 07/20/2010 12:56 PM, Flik Shen wrote: > Hi, > > I set the local port of server to 4000 without other change and start server > on box 10.X.X.1. > I could successfully run demo case "SimpleTestPlan.jmx" by below instruction. > Jmeter -n -t SimpleTestPlan.jmx -l log.jtl -R 127.0.0.1 > Following messages are returned. > Created the tree successfully using SimpleTestPlan.jmx > Configuring remote engine for 127.0.0.1 > Using remote object: UnicastRef [liveRef: > [endpoint:[10.X.X.1:4000](remote),objID:[2a4874c0:129ef46746f:-8000, 0]]] > Starting remote engines > Starting the test @ Tue Jul 20 10:25:28 GMT 2010 (1279621528920) > Remote engines have been started > Tidying up ... @ Tue Jul 20 10:25:29 GMT 2010 (1279621529636) > ... end of run > > I build SSH tunnel on both 1099 and 4000 on my box whose IP is 192.X.X.1 to > remote server. > And run following command. > Jmeter -n -t SimpleTestPlan.jmx -l log.jtl -R 127.0.0.1 > And below messages are got and stuck there. > Created the tree successfully using SimpleTestPlan.jmx > Configuring remote engine for 127.0.0.1 > Using remote object: UnicastRef [liveRef: > [endpoint:[10.X.X.1:4000](remote),objID:[2a4874c0:129ef46746f:-8000, 0]]] > Starting remote engines > Starting the test @ Tue Jul 20 18:32:19 CST 2010 (1279621939513) > Remote engines have been started > I found there is exception occurs in log file. > 2010/07/20 18:32:34 ERROR - jmeter.engine.ClientJMeterEngine: > java.rmi.ConnectIOException: Exception creating connection to: 10.X.X.1; > nested exception is: > java.net.NoRouteToHostException: connect timed out: 10.X.X.1 > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:587) > at > sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185) > at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94) > at > org.apache.jmeter.engine.RemoteJMeterEngineImpl_Stub.configure(Unknown Source) > at > org.apache.jmeter.engine.ClientJMeterEngine.run(ClientJMeterEngine.java:122) > at java.lang.Thread.run(Thread.java:613) > Caused by: java.net.NoRouteToHostException: connect timed out: 10.X.X.1 > at > sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:187) > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569) > ... 6 more > > I guess to provide facilities, Jmeter Server might registry its IP address > and port in RMI server. > Client will use this information to communicate with Jmeter Server. > The disadvantage is client could not reach remote server by IP address > through SSH Tunnel automatically after it fetches remote server IP address. > > Base on above I guess Jmeter Client and Server could not work through SSH > Tunnel. > > If I am wrong, please correct me. > > Thanks and best regards, > Flik --------------------------------------------------------------------- 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]
