Flik, Have you tried this without SSH tunneling(probably you might have to disable firewall for 1099 and 4000 ports. Trust me, its worth giving a try). The aim here is not the avoid using SSH but to determine if the problem is with SSH tunneling or whether its with the basic jmeter client-server communication itself. Once your sure that jmeter client-server communication works without SSH, then you can start working towards nailing down the problem with RMI over SSH process. Without which you would be trying to find a needle in the haystack(or in the stack-trace ;) ) which is obviously painful.
-Chaitanya M Bhatt http://www.performancecompetence.com 2010/7/21 Flik Shen <flik_s...@infosys.com> > Hi Felix, > > I didn't share you enough information and misled you. > It is all my fault. > Below are section of jmeter log file. > It seems client had successfully obtain IP address of Jmeter server. > As the IP address, I guess client will try to communicate server directly. > I tried to add route for remote 10.108.44.1 by command "route add -host > 10.108.44.1 127.0.0.1" > It still could not work and error becomes SocketTimeOutException read time > out. > I wonder whether there is a way client could directly touch server without > intermediary RMI registry server. > > 2010/07/20 18:32:02 INFO - jmeter.JMeter: Loading file: SimpleTestPlan.jmx > 2010/07/20 18:32:02 INFO - jmeter.save.SaveService: Testplan (JMX) > version: 2.2. Testlog (JTL) version: 2.2 > 2010/07/20 18:32:02 INFO - jmeter.save.SaveService: Using SaveService > properties file encoding UTF-8 > 2010/07/20 18:32:02 INFO - jmeter.save.SaveService: Using SaveService > properties file version 697317 > 2010/07/20 18:32:02 INFO - jmeter.save.SaveService: Using SaveService > properties version 2.1 > 2010/07/20 18:32:02 INFO - jmeter.save.SaveService: All converter versions > present and correct > 2010/07/20 18:32:02 INFO - jmeter.samplers.SampleResult: Note: Sample > TimeStamps are START times > 2010/07/20 18:32:02 INFO - jmeter.samplers.SampleResult: > sampleresult.default.encoding is set to ISO-8859-1 > 2010/07/20 18:32:02 INFO - jmeter.protocol.http.sampler.HTTPSamplerBase: > Cannot find .className property for htmlParser, using default > 2010/07/20 18:32:02 INFO - jmeter.protocol.http.sampler.HTTPSamplerBase: > Parser for text/html is > 2010/07/20 18:32:02 INFO - jmeter.protocol.http.sampler.HTTPSamplerBase: > Parser for application/xhtml+xml is > 2010/07/20 18:32:02 INFO - jmeter.protocol.http.sampler.HTTPSamplerBase: > Parser for application/xml is > 2010/07/20 18:32:02 INFO - jmeter.protocol.http.sampler.HTTPSamplerBase: > Parser for text/xml is > 2010/07/20 18:32:02 INFO - jmeter.protocol.http.sampler.HTTPSamplerBase: > Parser for text/vnd.wap.wml is > org.apache.jmeter.protocol.http.parser.RegexpHTMLParser > 2010/07/20 18:32:02 INFO - jmeter.protocol.http.sampler.HTTPSampler: > Maximum connection retries = 10 > 2010/07/20 18:32:02 INFO - jmeter.protocol.http.sampler.HTTPSampler: > Connection and read timeouts are available on this JVM > 2010/07/20 18:32:02 INFO - jmeter.JMeter: Configuring remote engine for > 127.0.0.1 > 2010/07/20 18:32:19 INFO - jmeter.engine.ClientJMeterEngine: about to run > remote test on 127.0.0.1 > 2010/07/20 18:32:19 INFO - jmeter.engine.ClientJMeterEngine: done > initiating run command > 2010/07/20 18:32:19 INFO - jmeter.engine.ClientJMeterEngine: running > clientengine run method > 2010/07/20 18:32:19 INFO - jmeter.engine.util.CompoundVariable: Note: > Function class names must contain the string: '.functions.' > 2010/07/20 18:32:19 INFO - jmeter.engine.util.CompoundVariable: Note: > Function class names must not contain the string: '.gui.' > 2010/07/20 18:32:19 INFO - jmeter.engine.ConvertListeners: num threads = > 10 > 2010/07/20 18:32:19 INFO - jmeter.samplers.StandardSampleSender: Using > Standard Remote Sampler for this test run > 2010/07/20 18:32:19 INFO - jmeter.samplers.StandardSampleSender: Using > Standard Remote Sampler for this test run > 2010/07/20 18:32:34 ERROR - jmeter.engine.ClientJMeterEngine: > java.rmi.ConnectIOException: Exception creating connection to: 10.108.44.1; > nested exception is: > java.net.NoRouteToHostException: connect timed out: 10.108.44.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: > 17.108.44.149 > at > sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:187) > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569) > ... 6 more > > Thanks and best regards, > Flik > > On 7/21/10 2:55 PM, "Felix Frank" <f...@mpexnet.de> wrote: > > Flik, > > On 07/21/2010 06:18 AM, Flik Shen wrote: > > 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? > > Ah, sorry, I missed the bit about you setting the server port manually. > Good idea that. > > > 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. > > That rings a bell. I remember a lot of fuss with wrong host name > resolutions. Try adding aliases to 127.0.0.1 that correspond to the > Jmeter Server on your Jmeter controlling host (the one initiating remote > execution) to the /etc/hosts file (this assumes *nix, not sure how to do > this in Windows). > The remote host may or may not also be aware of the details of the peer. > > To clarify, the /etc/hosts file on your box host should probably look like > 127.0.0.1 localhost jmeter1 > 192.168.0.1 desktop > or somesuch, assuming your jmeter server knows itself as "jmeter1". > > HTH > Felix > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > > > > **************** CAUTION - Disclaimer ***************** > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended > solely > for the use of the addressee(s). If you are not the intended recipient, > please > notify the sender by e-mail and delete the original message. Further, you > are not > to copy, disclose, or distribute this e-mail or its contents to any other > person and > any such actions are unlawful. This e-mail may contain viruses. Infosys has > taken > every reasonable precaution to minimize this risk, but is not liable for > any damage > you may sustain as a result of any virus in this e-mail. You should carry > out your > own virus checks before opening the e-mail or attachment. Infosys reserves > the > right to monitor and review the content of all messages sent to or from > this e-mail > address. Messages sent to or from this e-mail address may be stored on the > Infosys e-mail system. > ***INFOSYS******** End of Disclaimer ********INFOSYS*** > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
