You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by ECNiz <ec...@charter.net> on 2007/09/08 04:51:00 UTC
Distributed Testing Windows GUI/RHEL Servers Not Working
I'm trying to setup a JMeter Distributed test. I have 4 Machines, 2 Running
windows 2003 Server and 2 Running Redhat Enterprise Linux 4.
All 4 machines are Using:
JMeter 2.3RC4
JDK 1.6.0_02
They are all on the same subnet.
I am using one of the Windows machines in GUI mode as a controller. It will
control the other Windows machine, but neither of the RHEL servers. I see
no problems in the RHEL jmeter.log files (The last line reads: ... Bound to
registry on port 1099) so I'm assuming the servers are up.
I have the firewall disabled.
>From the Controller machine I can telnet to port 1099 on the RHEL server, so
I know the connection is open.
Does anyone have an experience with this type of configuration or have any
suggestions you may be able to give me?
Or, do you have any techniques I may be able to use to debug this problem?
Thank You!
-Erik
--
View this message in context: http://www.nabble.com/Distributed-Testing-Windows-GUI-RHEL-Servers-Not-Working-tf4404727.html#a12566254
Sent from the JMeter - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Distributed Testing Windows GUI/RHEL Servers Not Working
Posted by sebb <se...@gmail.com>.
Thanks - I'll see about adding the info to the documentation.
On 10/09/2007, ECNiz <ec...@charter.net> wrote:
>
> Thank you for your suggestions sebb, but none of those were the problem.
>
> In my log, I had:
>
> ERROR - jmeter.engine.ClientJMeterEngine: java.rmi.ConnectException:
> Connection refused to host: 127.0.0.1;
>
> After some more digging on the web, I found this thread:
>
> http://forum.java.sun.com/thread.jspa?threadID=288759&messageID=2518854
>
> dealing with the same problem with rmi registry.
>
> To sum it up, the problem only occurred when mixing windows and linux
> machines.
> The linux machines were returning 127.0.0.1 as their address, and then the
> windows machine
> would try to connect to 127.0.0.1 which obviously would fail.
>
> To correct this problem, when I started the server, I used the flag
> -Djava.rmi.server.hostname=xxx.xxx.xxx.xxx
>
> where the xxx's equal the ip address of that machine on which I'm starting
> the server.
>
> -Erik
>
>
>
> sebb-2 wrote:
> >
> > On 08/09/2007, ECNiz <ec...@charter.net> wrote:
> >>
> >> I'm trying to setup a JMeter Distributed test. I have 4 Machines, 2
> >> Running
> >> windows 2003 Server and 2 Running Redhat Enterprise Linux 4.
> >>
> >> All 4 machines are Using:
> >> JMeter 2.3RC4
> >> JDK 1.6.0_02
> >
> > Presumably these are all from the same supplier?
> >
> >> They are all on the same subnet.
> >>
> >> I am using one of the Windows machines in GUI mode as a controller. It
> >> will
> >> control the other Windows machine, but neither of the RHEL servers. I
> >> see
> >> no problems in the RHEL jmeter.log files (The last line reads: ... Bound
> >> to
> >> registry on port 1099) so I'm assuming the servers are up.
> >
> > Yes.
> >
> >> I have the firewall disabled.
> >> From the Controller machine I can telnet to port 1099 on the RHEL server,
> >> so
> >> I know the connection is open.
> >>
> >> Does anyone have an experience with this type of configuration or have
> >> any
> >> suggestions you may be able to give me?
> >
> > Do any of the installation paths have spaces in them?
> >
> > What does the client GUI log have to say about the connection?
> >
> > By the way, the new -R flag is useful for testing remote servers - no
> > need to edit the properties file.
> >
> >> Or, do you have any techniques I may be able to use to debug this
> >> problem?
> >>
> >> Thank You!
> >> -Erik
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Distributed-Testing-Windows-GUI-RHEL-Servers-Not-Working-tf4404727.html#a12566254
> >> Sent from the JMeter - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Distributed-Testing-Windows-GUI-RHEL-Servers-Not-Working-tf4404727.html#a12599323
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Distributed Testing Windows GUI/RHEL Servers Not Working
Posted by ECNiz <ec...@charter.net>.
Thank you for your suggestions sebb, but none of those were the problem.
In my log, I had:
ERROR - jmeter.engine.ClientJMeterEngine: java.rmi.ConnectException:
Connection refused to host: 127.0.0.1;
After some more digging on the web, I found this thread:
http://forum.java.sun.com/thread.jspa?threadID=288759&messageID=2518854
dealing with the same problem with rmi registry.
To sum it up, the problem only occurred when mixing windows and linux
machines.
The linux machines were returning 127.0.0.1 as their address, and then the
windows machine
would try to connect to 127.0.0.1 which obviously would fail.
To correct this problem, when I started the server, I used the flag
-Djava.rmi.server.hostname=xxx.xxx.xxx.xxx
where the xxx's equal the ip address of that machine on which I'm starting
the server.
-Erik
sebb-2 wrote:
>
> On 08/09/2007, ECNiz <ec...@charter.net> wrote:
>>
>> I'm trying to setup a JMeter Distributed test. I have 4 Machines, 2
>> Running
>> windows 2003 Server and 2 Running Redhat Enterprise Linux 4.
>>
>> All 4 machines are Using:
>> JMeter 2.3RC4
>> JDK 1.6.0_02
>
> Presumably these are all from the same supplier?
>
>> They are all on the same subnet.
>>
>> I am using one of the Windows machines in GUI mode as a controller. It
>> will
>> control the other Windows machine, but neither of the RHEL servers. I
>> see
>> no problems in the RHEL jmeter.log files (The last line reads: ... Bound
>> to
>> registry on port 1099) so I'm assuming the servers are up.
>
> Yes.
>
>> I have the firewall disabled.
>> From the Controller machine I can telnet to port 1099 on the RHEL server,
>> so
>> I know the connection is open.
>>
>> Does anyone have an experience with this type of configuration or have
>> any
>> suggestions you may be able to give me?
>
> Do any of the installation paths have spaces in them?
>
> What does the client GUI log have to say about the connection?
>
> By the way, the new -R flag is useful for testing remote servers - no
> need to edit the properties file.
>
>> Or, do you have any techniques I may be able to use to debug this
>> problem?
>>
>> Thank You!
>> -Erik
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Distributed-Testing-Windows-GUI-RHEL-Servers-Not-Working-tf4404727.html#a12566254
>> Sent from the JMeter - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Distributed-Testing-Windows-GUI-RHEL-Servers-Not-Working-tf4404727.html#a12599323
Sent from the JMeter - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Distributed Testing Windows GUI/RHEL Servers Not Working
Posted by sebb <se...@gmail.com>.
On 08/09/2007, ECNiz <ec...@charter.net> wrote:
>
> I'm trying to setup a JMeter Distributed test. I have 4 Machines, 2 Running
> windows 2003 Server and 2 Running Redhat Enterprise Linux 4.
>
> All 4 machines are Using:
> JMeter 2.3RC4
> JDK 1.6.0_02
Presumably these are all from the same supplier?
> They are all on the same subnet.
>
> I am using one of the Windows machines in GUI mode as a controller. It will
> control the other Windows machine, but neither of the RHEL servers. I see
> no problems in the RHEL jmeter.log files (The last line reads: ... Bound to
> registry on port 1099) so I'm assuming the servers are up.
Yes.
> I have the firewall disabled.
> From the Controller machine I can telnet to port 1099 on the RHEL server, so
> I know the connection is open.
>
> Does anyone have an experience with this type of configuration or have any
> suggestions you may be able to give me?
Do any of the installation paths have spaces in them?
What does the client GUI log have to say about the connection?
By the way, the new -R flag is useful for testing remote servers - no
need to edit the properties file.
> Or, do you have any techniques I may be able to use to debug this problem?
>
> Thank You!
> -Erik
>
> --
> View this message in context: http://www.nabble.com/Distributed-Testing-Windows-GUI-RHEL-Servers-Not-Working-tf4404727.html#a12566254
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org