Hi sebb,
thanks for your quick reply. I have definitly removed the 127.0.0.1 entry from the remote_hosts property setting.
I just tried a jmeter-setup on my local network and it work exactly the way it should.
What I noticed is this:
Watching the jmeter.log file of my server-machine, it states:
2004/10/27 22:21:09 DEBUG - jmeter.engine.RemoteJMeterEngineImpl: This = org.apache.jmeter.engine.RemoteJMeterEngineImpl [RemoteStub [ref: [endpoint:[192.168.2.103:49314])local=,objID:[0]]]]
So the external IP is logged, not the local loopback address (127.0.0.1).
Comparing this to my previous results on the test environment, there is the loopback IP stated in the logfile:
2004/10/27 18:10:27 DEBUG - jmeter.engine.RemoteJMeterEngineImpl: This =
org.apache.jmeter.engine.RemoteJMeterEngineImpl[RemoteStub [ref:
[endpoint:[127.0.0.1:54315](local),objID:[0]]]]
I tracked this down within the source files. To my mind, the call to
INetAddress.getLocalHost().getHostAddress() seems to return not the external IP but the loopback IP.
I know this is somewhat of the scope of this mailing list, but maybe someone has got an idea, what may cause this behaviour. Could be the host-file on the server-machine ?
Anyway, thanks for your help. Regards.
christian
Am 27.10.2004 um 18:38 schrieb sebb:
On Wed, 27 Oct 2004 18:07:56 +0200 (MEST), Christian Schwanke <[EMAIL PROTECTED]> wrote:Hi,
I successfully ran a testplan locally.
Now I want to run the testplan on a remote machine.
I followed the instructions from the manual and started the
jmeter-server--Skript (which - as I understand - launches the rmiregistry).
Yes, it launches both the registry and the jmeter server
The log file on the remote machine states:
2004/10/27 18:10:27 INFO - jmeter.JMeter: Version 2.0.1
2004/10/27 18:10:27 INFO - jmeter.JMeter: java.version=1.4.2
2004/10/27 18:10:27 INFO - jmeter.engine.RemoteJMeterEngineImpl: Starting
backing engine
2004/10/27 18:10:27 DEBUG - jmeter.engine.RemoteJMeterEngineImpl: This =
org.apache.jmeter.engine.RemoteJMeterEngineImpl[RemoteStub [ref:
[endpoint:[127.0.0.1:54315](local),objID:[0]]]]
Remark: I'm not sure wether the 127.0.0.1 is correct here ?
I then launched the JMeter-Client on my local machine specifying the remote
host name of the server in the properties-file (remote_hosts-property).
the GUI offers the correct hostname within the remote start-submenu.
However, when commencing a remote test, the following error is logged
locally:
2004/10/27 18:00:23 ERROR - jmeter.engine.ClientJMeterEngine:
java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested
exception is:
This looks wrong - the client should try to connect to the remote system.
Could be an error in the remote_hosts property, or perhaps a DNS
resolution error.
Or did you perhaps leave in the 127.0.0.1 entry and do a remote start all?
What does jmeter.log say just before this error? It might say what host name it was trying to use.
java.net.ConnectException: Connection refused: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.apache.jmeter.engine.RemoteJMeterEngineImpl_Stub.setHost(Unknown
Source)
at
org.apache.jmeter.engine.ClientJMeterEngine.run(ClientJMeterEngine.jav a:136)
at java.lang.Thread.run(Unknown Source)
I'm pretty sure that there is a simple solution to this problem, but I just
can't figure it out.
I don't know much about RMI, e.g. if I need to start a rmiregistry locally
as well.
I don't think so.
Any advice is appreciated,
Thanks, Christian
--------------------------------------------------------------------- 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]
