Great, that fixed it. I have changed the entry in the /etc/hosts to map directly to my actual IP address and it worked out.

sebb wrote:
On 26 August 2010 12:58, Alexander Fedulov
<[email protected]> wrote:
Thanks for the quick answer. Both machines are in the same subnet so, I
suppose, the problem is not the network directly.
It seems to be some configuration problem. That is what I found in the
jmeter-server.log on the remote machine:

2010/08/26 13:47:56 INFO  - jmeter.samplers.RemoteListenerWrapper: Test
Started on 10.147.67.221
2010/08/26 13:47:56 ERROR - jmeter.samplers.RemoteListenerWrapper:
testStarted(host) java.rmi.ConnectException: Connection refused to host:
127.0.1.1; nested exception is:
  java.net.ConnectException: Connection refused

I do net really get it, why it tries to establish the connection to the
localhost at this point. Could it be something, that comes from the testplan
configuration file of the client?

No, that's a hosts file problem.

The client tries to find out its own hostname, and sends that to the
server as the return address.

sebb wrote:
On 26 August 2010 11:25, Alexander Fedulov
<[email protected]> wrote:

Hi all.

I am using jmeter-2.4 and trying to perform the remote test execution.
Whenever my test plan contains a listener, only one request is sent
(instead
of, say 5, that where specified in the plan). I have tried changing the
mode
to Hold on the remote machine , but it did not fix the problem. Would
appreciate your help.

That sounds like a network configuration problem - are there any
routers etc between your client and server systems?

Check the JMeter logs on both client and server.

Try running the same test with the client and server on the same network.


Best regards
Alexander Fedulov

---------------------------------------------------------------------
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]

Reply via email to