Matt Wlazlo | 3 Oct 02:30 2006
Picon

distributed testing woes

Hi,

I'm tearing my hair out trying to get distributed testing working.

I have a simple configuration:

Console: matt.domain
remote_hosts=java.domain

Slave: java.domain
(default configuration)

I run the server like this (after rmiregistry 1099&):
./jmeter -Dserver_port=1099 -Djava.rmi.server.hostname=java.domain -s

But I always get the following error on the server:

2006/10/03 00:00:10 INFO  - jmeter.samplers.RemoteListenerWrapper:
Test Started on java.domain:1099
2006/10/03 00:00:10 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
        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
        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.samplers.RemoteSampleListenerImpl_Stub.testStarted(Unknown
Source)
        at org.apache.jmeter.samplers.RemoteListenerWrapper.testStarted(RemoteListenerWrapper.java:74)
(Continue reading)

Peter Lin | 3 Oct 02:47 2006
Picon

Re: distributed testing woes

did you read the tutorial?

http://jakarta.apache.org/jmeter/usermanual/jmeter_distributed_testing_step_by_step.pdf

peter

On 10/2/06, Matt Wlazlo <mwlazlo <at> gmail.com> wrote:
>
> Hi,
>
> I'm tearing my hair out trying to get distributed testing working.
>
> I have a simple configuration:
>
> Console: matt.domain
> remote_hosts=java.domain
>
> Slave: java.domain
> (default configuration)
>
> I run the server like this (after rmiregistry 1099&):
> ./jmeter -Dserver_port=1099 -Djava.rmi.server.hostname=java.domain -s
>
> But I always get the following error on the server:
>
> 2006/10/03 00:00:10 INFO  - jmeter.samplers.RemoteListenerWrapper:
> Test Started on java.domain:1099
> 2006/10/03 00:00:10 ERROR - jmeter.samplers.RemoteListenerWrapper:
> testStarted(host) java.rmi.ConnectException: Connection refused to
> host: 127.0.1.1; nested exception is:
(Continue reading)

Matt Wlazlo | 3 Oct 02:54 2006
Picon

Re: distributed testing woes

Yeah, that's the example configuration I used...

matt

On 10/3/06, Peter Lin <woolfel <at> gmail.com> wrote:
> did you read the tutorial?
>
> http://jakarta.apache.org/jmeter/usermanual/jmeter_distributed_testing_step_by_step.pdf
>
> peter
>
>
> On 10/2/06, Matt Wlazlo <mwlazlo <at> gmail.com> wrote:
> >
> > Hi,
> >
> > I'm tearing my hair out trying to get distributed testing working.
> >
> > I have a simple configuration:
> >
> > Console: matt.domain
> > remote_hosts=java.domain
> >
> > Slave: java.domain
> > (default configuration)
> >
> > I run the server like this (after rmiregistry 1099&):
> > ./jmeter -Dserver_port=1099 -Djava.rmi.server.hostname=java.domain -s
> >
> > But I always get the following error on the server:
(Continue reading)

Matt Wlazlo | 3 Oct 02:59 2006
Picon

Re: distributed testing woes

The thing I really can't understand, and which I think is the problem,
is that the server is trying to connect to 127.0.1.1 for some reason.
It's probably just my incomplete knowlege of RMI, but shouldn't the
console be the one having problems to connect (via RMI) if anything is
wrong?

*boggle*

Matt

On 10/3/06, Peter Lin <woolfel <at> gmail.com> wrote:
> did you read the tutorial?
>
> http://jakarta.apache.org/jmeter/usermanual/jmeter_distributed_testing_step_by_step.pdf
>
> peter
>
>
> On 10/2/06, Matt Wlazlo <mwlazlo <at> gmail.com> wrote:
> >
> > Hi,
> >
> > I'm tearing my hair out trying to get distributed testing working.
> >
> > I have a simple configuration:
> >
> > Console: matt.domain
> > remote_hosts=java.domain
> >
> > Slave: java.domain
(Continue reading)

McCune, Tim | 3 Oct 03:22 2006
Picon

Remote testing hangs

I'm trying to set up my first JMeter test that is using remote clients.  My
environment consists of a Windows machine and a Linux machine.  I have
started jmeter-server on both machines.  When I do a "remote start" on the
same machine that I'm running the GUI on, everything works fine.  When I try
to do a "remote start" on the other box, it doesn't work.  On the Linux box,
JMeter freezes up completely.  On the Windows box, the GUI continues to
work; it just acts like nothing has happened.  No results.  I've tried
turning on debugging, but there's nothing informative in the logs.  Any
suggestions would be appreciated.

Thanks.

--Tim

Peter Lin | 3 Oct 03:21 2006
Picon

Re: distributed testing woes

127.0.0.1 is the loop back, which is there for an example.

you need to replace that with the IP's of the systems. go through page 2
step-by-step and it will work.

peter

On 10/2/06, Matt Wlazlo <mwlazlo <at> gmail.com> wrote:
>
> The thing I really can't understand, and which I think is the problem,
> is that the server is trying to connect to 127.0.1.1 for some reason.
> It's probably just my incomplete knowlege of RMI, but shouldn't the
> console be the one having problems to connect (via RMI) if anything is
> wrong?
>
> *boggle*
>
> Matt
>
> On 10/3/06, Peter Lin <woolfel <at> gmail.com> wrote:
> > did you read the tutorial?
> >
> >
> http://jakarta.apache.org/jmeter/usermanual/jmeter_distributed_testing_step_by_step.pdf
> >
> > peter
> >
> >
> > On 10/2/06, Matt Wlazlo <mwlazlo <at> gmail.com> wrote:
> > >
(Continue reading)

Matt Wlazlo | 3 Oct 03:28 2006
Picon

Re: distributed testing woes

Yup, that's why I have:

remote_hosts=java.domain

which resolves to an IP that does exist and is pingable :-)

On the server, remote_hosts is commented out; is that right? It's not
mentioned in the tutorial..

matt

On 10/3/06, Peter Lin <woolfel <at> gmail.com> wrote:
> 127.0.0.1 is the loop back, which is there for an example.
>
> you need to replace that with the IP's of the systems. go through page 2
> step-by-step and it will work.
>
> peter
>
> On 10/2/06, Matt Wlazlo <mwlazlo <at> gmail.com> wrote:
> >
> > The thing I really can't understand, and which I think is the problem,
> > is that the server is trying to connect to 127.0.1.1 for some reason.
> > It's probably just my incomplete knowlege of RMI, but shouldn't the
> > console be the one having problems to connect (via RMI) if anything is
> > wrong?
> >
> > *boggle*
> >
> > Matt
(Continue reading)

Rajesh Balamohan | 3 Oct 03:35 2006

Re: Remote testing hangs

Couple of things you may want to check.

1. Ensure that 127.0.0.1 is not there in /etc/hosts file in both server
and client.
2. Ensure that your jmeter-server is running in linux box.
3. Ensure that you are able to ping the client box from your server.

What do you mean by freezing?. Does the CPU utilization go high in the
client? Is the server trying to contact the client?. If you look at the
logs, you can come to know about this.

Did you try taking any thread-dump when you said its freezing?. do a "kill
-QUIT <pid of linux jmeter-server>" to get a threaddump.

> I'm trying to set up my first JMeter test that is using remote clients.
> My
> environment consists of a Windows machine and a Linux machine.  I have
> started jmeter-server on both machines.  When I do a "remote start" on the
> same machine that I'm running the GUI on, everything works fine.  When I
> try
> to do a "remote start" on the other box, it doesn't work.  On the Linux
> box,
> JMeter freezes up completely.  On the Windows box, the GUI continues to
> work; it just acts like nothing has happened.  No results.  I've tried
> turning on debugging, but there's nothing informative in the logs.  Any
> suggestions would be appreciated.
>
>
>
> Thanks.
(Continue reading)

Peter Lin | 3 Oct 03:36 2006
Picon

Re: distributed testing woes

don't use a domain. use the IP address. using a domain may cause weirdness.

list all the ip addresses for the systems running jmeter-server.bat.

if you're running both jmeter-server.bat and jmeter.bat, list the IP of the
system. it would be easier to diagnose your problem, if you include more
details like number of systems, each system's IP and the settings in each
system.

peter

On 10/2/06, Matt Wlazlo <mwlazlo <at> gmail.com> wrote:
>
> Yup, that's why I have:
>
> remote_hosts=java.domain
>
> which resolves to an IP that does exist and is pingable :-)
>
> On the server, remote_hosts is commented out; is that right? It's not
> mentioned in the tutorial..
>
> matt
>
> On 10/3/06, Peter Lin <woolfel <at> gmail.com> wrote:
> > 127.0.0.1 is the loop back, which is there for an example.
> >
> > you need to replace that with the IP's of the systems. go through page 2
> > step-by-step and it will work.
> >
(Continue reading)

Matt Wlazlo | 3 Oct 03:37 2006
Picon

Re: distributed testing woes

FTR, I also get the message 'jmeter.engine.RemoteJMeterEngineImpl:
Starting backing engine on 1099' on the server, so it's starting up
fine.

Also, I tried running the server with -Djava.rmi.server.logCalls=true
and got the following, maybe it will help?

NP 10.21.62.137=matt.domain

Oct 3, 2006 12:45:04 AM sun.rmi.server.UnicastServerRef logCall
FINER: RMI TCP Connection(5)-10.21.62.137: [10.21.62.137:
sun.rmi.transport.DGCImpl[0:0:0, 2]: java.rmi.dgc.Lease
dirty(java.rmi.server.ObjID[], long, java.rmi.dgc.Lease)]
Oct 3, 2006 12:45:04 AM sun.rmi.server.UnicastServerRef logCall
FINER: RMI TCP Connection(5)-10.21.62.137: [10.21.62.137:
org.apache.jmeter.engine.RemoteJMeterEngineImpl[0]: public abstract
void org.apache.jmeter.engine.RemoteJMeterEngine.reset() throws
java.rmi.RemoteException]
Oct 3, 2006 12:45:04 AM sun.rmi.server.UnicastServerRef logCall
FINER: RMI TCP Connection(5)-10.21.62.137: [10.21.62.137:
org.apache.jmeter.engine.RemoteJMeterEngineImpl[0]: public abstract
void org.apache.jmeter.engine.RemoteJMeterEngine.setHost(java.lang.String)
throws java.rmi.RemoteException]
Oct 3, 2006 12:45:05 AM sun.rmi.server.UnicastServerRef logCall
FINER: RMI TCP Connection(5)-10.21.62.137: [10.21.62.137:
org.apache.jmeter.engine.RemoteJMeterEngineImpl[0]: public abstract
void org.apache.jmeter.engine.RemoteJMeterEngine.configure(org.apache.jorphan.collections.HashTree)
throws java.rmi.RemoteException]
Oct 3, 2006 12:45:05 AM sun.rmi.server.UnicastServerRef logCall
FINER: RMI TCP Connection(5)-10.21.62.137: [10.21.62.137:
(Continue reading)


Gmane