You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Jacob Singh <ja...@gmail.com> on 2008/09/24 06:59:56 UTC
Changing the hostname jmeter-server reports to the client
Hello,
I'm trying to get distributed search working on ec2 (if anyone has any
results here, would love to hear them). Here's what I've got going:
The public IP is 75.101.209.34
and the private IP is 10.252.162.18
----
jmeter log
----
My client can connect when the server is running, and I can telnet in,
but then has an issue here:
2008/09/24 08:55:40 INFO - jmeter.samplers.StandardSampleSender:
Using Standard Remote Sampler for this test run
2008/09/24 08:58:49 ERROR - jmeter.engine.ClientJMeterEngine:
java.rmi.ConnectException: Connection refused to host: 10.252.162.18;
nested exception is:
java.net.ConnectException: Connection timed out
------------------------------------
Obviously, the server is sending the wrong IP address to the client.
As you can see below, I am setting the rmi.server.hostname property
and it is taking effect, however jmeter stubbornly refuses to actually
treat this as its IP...
----
jmeter-server log
----
2008/09/24 00:34:50 INFO - jmeter.JMeter: Setting System property:
java.rmi.server.hostname=75.101.209.34
2008/09/24 00:34:50 INFO - jmeter.JMeter: Setting System property:
server_port=1099
2008/09/24 00:34:50 INFO - jmeter.JMeter: Copyright (c) 1998-2008 The
Apache Software Foundation
2008/09/24 00:34:50 INFO - jmeter.JMeter: Version 2.3.2 r665936
2008/09/24 00:34:50 INFO - jmeter.JMeter: java.version=1.6.0_04
2008/09/24 00:34:50 INFO - jmeter.JMeter: java.vm.name=Java
HotSpot(TM) Server VM
2008/09/24 00:34:50 INFO - jmeter.JMeter: os.name=Linux
2008/09/24 00:34:50 INFO - jmeter.JMeter: os.arch=i386
2008/09/24 00:34:50 INFO - jmeter.JMeter: os.version=2.6.18-xenU-ec2-v1.0
2008/09/24 00:34:50 INFO - jmeter.JMeter: file.encoding=UTF-8
2008/09/24 00:34:50 INFO - jmeter.JMeter: Default Locale=English
(United States)
2008/09/24 00:34:50 INFO - jmeter.JMeter: JMeter Locale=English
(United States)
2008/09/24 00:34:50 INFO - jmeter.JMeter:
JMeterHome=/usr/local/jakarta-jmeter-2.3.2
2008/09/24 00:34:50 INFO - jmeter.JMeter: user.dir
=/usr/local/jakarta-jmeter-2.3.2
2008/09/24 00:34:50 INFO - jmeter.JMeter: PWD
=/usr/local/jakarta-jmeter-2.3.2
2008/09/24 00:34:50 INFO - jmeter.JMeter: IP: 10.252.162.18 Name:
domU-12-31-38-00-9D-E4.compute-1.internal FullName:
domU-12-31-38-00-9D-E4.compute-1.internal
2008/09/24 00:34:51 INFO - jmeter.engine.RemoteJMeterEngineImpl:
Starting backing engine on 1099
2008/09/24 00:34:51 INFO - jmeter.engine.RemoteJMeterEngineImpl: IP
address=10.252.162.18
-------------------------
I think one of the issues is that ec2 doesn't actually know that this
is its ip because it is obviously behind a router. So even if you
ping its public DNS, it will return the private domain.
Can someone throw me a bone here? I've spent about 6hrs trying to fix
this, and I'm very sad because this will be awesome when it is working
:) I also plan to release an AMI at some point in the future.
--
+1 510 277-0891 (o)
+91 9999 33 7458 (m)
web: http://pajamadesign.com
Skype: pajamadesign
Yahoo: jacobsingh
AIM: jacobsingh
gTalk: jacobsingh@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Changing the hostname jmeter-server reports to the client
Posted by sebb <se...@gmail.com>.
On 25/09/2008, Jacob Singh <ja...@gmail.com> wrote:
> I'm not sure if I'm just missing this but...
>
> I set the RMI property as in the instructions, and this reportedly
> works fine. In fact, my master can contact the server.
> It's just that the server then passes a different IP back (not the one
> used by RMI), and the client in turn tries to use this IP.
That's RMI sending back the IP.
> Since it is a jmeter prop and not the RMI, is it possible to just
> override this somehow?
No, it's a system property - it has no effect on JMeter, only on RMI.
I don't know why this is not working.
> Best,
>
> Jacob
>
>
> On Fri, Sep 26, 2008 at 3:00 AM, sebb <se...@gmail.com> wrote:
> > On 25/09/2008, Jacob Singh <ja...@gmail.com> wrote:
> >> -------------------------
> >> >>
> >> >> I think one of the issues is that ec2 doesn't actually know that this
> >> >> is its ip because it is obviously behind a router. So even if you
> >> >> ping its public DNS, it will return the private domain.
> >> >> Can someone throw me a bone here? I've spent about 6hrs trying to fix
> >> >> this, and I'm very sad because this will be awesome when it is working
> >> >> :) I also plan to release an AMI at some point in the future.
> >> >>
> >> >
> >> > Can you get a simple EchoClient/Server working on that setup?
> >> >
> >> > Maybe that would give some pointers as to how to fix JMeter - e.g.
> >> > perhaps the RMI server needs to be run on the host given by the
> >> > rmi.server.hostname property.
> >> >
> >> > At present the property is not directly used by JMeter - it was
> >> > assumed that the Java RMI would know what to do when the property is
> >> > defined. Indeed that's what the documentation suggests here:
> >> >
> >> > http://java.sun.com/docs/books/tutorial/rmi/running.html
> >> >
> >>
> >>
> >> Hi Sebb,
> >>
> >> Thanks for the quick response. After many hours of googling, I've got
> >> to say, you've got my vote for maintainer of the year!
> >>
> >> I'm not sure what EchoClient/Server means. I know it is a java lib of
> >> some sort, but I'm not a Java programmer, so I don't know how to
> >> proceed here.
> >
> > The EchoClient is a sample RMI application - you can find it on the
> > Sun Java website, e.g.
> >
> > http://java.sun.com/developer/JDCTechTips/2001/tt0227.html
> >
> >> I can read Java, but not write it too well. If you can tell me what
> >> you are looking for me to do, I will attempt it.
> >>
> >> Perhaps just allowing the hostname that the server passes back to use
> >> a Jmeter property would solve the whole thing.
> >
> > If only, but JMeter does not have much control over the RMI protocol.
> >
> >> I have resorted to running the whole thing in the cloud with the
> >> master acting in an ec2 instance, and the slaves in their own ec2
> >> instances, then rsyncing the jtls back to my desktop for the analysis.
> >> This is fine, but not preferred obviously as it is harder to modify
> >> the test, upload, etc...
> >>
> >> One other thing of note (you may want to add this to the remote instructions):
> >>
> >> When setting up the slaves, they have to have port 1099 open AND they
> >> need to be pingable (have ICMP open).
> >> If it is not open, it hangs with no error given.
> >>
> >> Best,
> >> Jacob
> >>
> >> --
> >>
> >>
> >> +1 510 277-0891 (o)
> >> +91 9999 33 7458 (m)
> >>
> >> web: http://pajamadesign.com
> >>
> >> Skype: pajamadesign
> >> Yahoo: jacobsingh
> >> AIM: jacobsingh
> >> gTalk: jacobsingh@gmail.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
> >
> >
>
>
>
>
> --
>
>
> +1 510 277-0891 (o)
> +91 9999 33 7458 (m)
>
> web: http://pajamadesign.com
>
> Skype: pajamadesign
> Yahoo: jacobsingh
> AIM: jacobsingh
> gTalk: jacobsingh@gmail.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: Changing the hostname jmeter-server reports to the client
Posted by Jacob Singh <ja...@gmail.com>.
I'm not sure if I'm just missing this but...
I set the RMI property as in the instructions, and this reportedly
works fine. In fact, my master can contact the server.
It's just that the server then passes a different IP back (not the one
used by RMI), and the client in turn tries to use this IP.
Since it is a jmeter prop and not the RMI, is it possible to just
override this somehow?
Best,
Jacob
On Fri, Sep 26, 2008 at 3:00 AM, sebb <se...@gmail.com> wrote:
> On 25/09/2008, Jacob Singh <ja...@gmail.com> wrote:
>> -------------------------
>> >>
>> >> I think one of the issues is that ec2 doesn't actually know that this
>> >> is its ip because it is obviously behind a router. So even if you
>> >> ping its public DNS, it will return the private domain.
>> >> Can someone throw me a bone here? I've spent about 6hrs trying to fix
>> >> this, and I'm very sad because this will be awesome when it is working
>> >> :) I also plan to release an AMI at some point in the future.
>> >>
>> >
>> > Can you get a simple EchoClient/Server working on that setup?
>> >
>> > Maybe that would give some pointers as to how to fix JMeter - e.g.
>> > perhaps the RMI server needs to be run on the host given by the
>> > rmi.server.hostname property.
>> >
>> > At present the property is not directly used by JMeter - it was
>> > assumed that the Java RMI would know what to do when the property is
>> > defined. Indeed that's what the documentation suggests here:
>> >
>> > http://java.sun.com/docs/books/tutorial/rmi/running.html
>> >
>>
>>
>> Hi Sebb,
>>
>> Thanks for the quick response. After many hours of googling, I've got
>> to say, you've got my vote for maintainer of the year!
>>
>> I'm not sure what EchoClient/Server means. I know it is a java lib of
>> some sort, but I'm not a Java programmer, so I don't know how to
>> proceed here.
>
> The EchoClient is a sample RMI application - you can find it on the
> Sun Java website, e.g.
>
> http://java.sun.com/developer/JDCTechTips/2001/tt0227.html
>
>> I can read Java, but not write it too well. If you can tell me what
>> you are looking for me to do, I will attempt it.
>>
>> Perhaps just allowing the hostname that the server passes back to use
>> a Jmeter property would solve the whole thing.
>
> If only, but JMeter does not have much control over the RMI protocol.
>
>> I have resorted to running the whole thing in the cloud with the
>> master acting in an ec2 instance, and the slaves in their own ec2
>> instances, then rsyncing the jtls back to my desktop for the analysis.
>> This is fine, but not preferred obviously as it is harder to modify
>> the test, upload, etc...
>>
>> One other thing of note (you may want to add this to the remote instructions):
>>
>> When setting up the slaves, they have to have port 1099 open AND they
>> need to be pingable (have ICMP open).
>> If it is not open, it hangs with no error given.
>>
>> Best,
>> Jacob
>>
>> --
>>
>>
>> +1 510 277-0891 (o)
>> +91 9999 33 7458 (m)
>>
>> web: http://pajamadesign.com
>>
>> Skype: pajamadesign
>> Yahoo: jacobsingh
>> AIM: jacobsingh
>> gTalk: jacobsingh@gmail.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
>
>
--
+1 510 277-0891 (o)
+91 9999 33 7458 (m)
web: http://pajamadesign.com
Skype: pajamadesign
Yahoo: jacobsingh
AIM: jacobsingh
gTalk: jacobsingh@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Changing the hostname jmeter-server reports to the client
Posted by sebb <se...@gmail.com>.
On 25/09/2008, Jacob Singh <ja...@gmail.com> wrote:
> -------------------------
> >>
> >> I think one of the issues is that ec2 doesn't actually know that this
> >> is its ip because it is obviously behind a router. So even if you
> >> ping its public DNS, it will return the private domain.
> >> Can someone throw me a bone here? I've spent about 6hrs trying to fix
> >> this, and I'm very sad because this will be awesome when it is working
> >> :) I also plan to release an AMI at some point in the future.
> >>
> >
> > Can you get a simple EchoClient/Server working on that setup?
> >
> > Maybe that would give some pointers as to how to fix JMeter - e.g.
> > perhaps the RMI server needs to be run on the host given by the
> > rmi.server.hostname property.
> >
> > At present the property is not directly used by JMeter - it was
> > assumed that the Java RMI would know what to do when the property is
> > defined. Indeed that's what the documentation suggests here:
> >
> > http://java.sun.com/docs/books/tutorial/rmi/running.html
> >
>
>
> Hi Sebb,
>
> Thanks for the quick response. After many hours of googling, I've got
> to say, you've got my vote for maintainer of the year!
>
> I'm not sure what EchoClient/Server means. I know it is a java lib of
> some sort, but I'm not a Java programmer, so I don't know how to
> proceed here.
The EchoClient is a sample RMI application - you can find it on the
Sun Java website, e.g.
http://java.sun.com/developer/JDCTechTips/2001/tt0227.html
> I can read Java, but not write it too well. If you can tell me what
> you are looking for me to do, I will attempt it.
>
> Perhaps just allowing the hostname that the server passes back to use
> a Jmeter property would solve the whole thing.
If only, but JMeter does not have much control over the RMI protocol.
> I have resorted to running the whole thing in the cloud with the
> master acting in an ec2 instance, and the slaves in their own ec2
> instances, then rsyncing the jtls back to my desktop for the analysis.
> This is fine, but not preferred obviously as it is harder to modify
> the test, upload, etc...
>
> One other thing of note (you may want to add this to the remote instructions):
>
> When setting up the slaves, they have to have port 1099 open AND they
> need to be pingable (have ICMP open).
> If it is not open, it hangs with no error given.
>
> Best,
> Jacob
>
> --
>
>
> +1 510 277-0891 (o)
> +91 9999 33 7458 (m)
>
> web: http://pajamadesign.com
>
> Skype: pajamadesign
> Yahoo: jacobsingh
> AIM: jacobsingh
> gTalk: jacobsingh@gmail.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: Changing the hostname jmeter-server reports to the client
Posted by Jacob Singh <ja...@gmail.com>.
-------------------------
>>
>> I think one of the issues is that ec2 doesn't actually know that this
>> is its ip because it is obviously behind a router. So even if you
>> ping its public DNS, it will return the private domain.
>> Can someone throw me a bone here? I've spent about 6hrs trying to fix
>> this, and I'm very sad because this will be awesome when it is working
>> :) I also plan to release an AMI at some point in the future.
>>
>
> Can you get a simple EchoClient/Server working on that setup?
>
> Maybe that would give some pointers as to how to fix JMeter - e.g.
> perhaps the RMI server needs to be run on the host given by the
> rmi.server.hostname property.
>
> At present the property is not directly used by JMeter - it was
> assumed that the Java RMI would know what to do when the property is
> defined. Indeed that's what the documentation suggests here:
>
> http://java.sun.com/docs/books/tutorial/rmi/running.html
>
Hi Sebb,
Thanks for the quick response. After many hours of googling, I've got
to say, you've got my vote for maintainer of the year!
I'm not sure what EchoClient/Server means. I know it is a java lib of
some sort, but I'm not a Java programmer, so I don't know how to
proceed here.
I can read Java, but not write it too well. If you can tell me what
you are looking for me to do, I will attempt it.
Perhaps just allowing the hostname that the server passes back to use
a Jmeter property would solve the whole thing.
I have resorted to running the whole thing in the cloud with the
master acting in an ec2 instance, and the slaves in their own ec2
instances, then rsyncing the jtls back to my desktop for the analysis.
This is fine, but not preferred obviously as it is harder to modify
the test, upload, etc...
One other thing of note (you may want to add this to the remote instructions):
When setting up the slaves, they have to have port 1099 open AND they
need to be pingable (have ICMP open).
If it is not open, it hangs with no error given.
Best,
Jacob
--
+1 510 277-0891 (o)
+91 9999 33 7458 (m)
web: http://pajamadesign.com
Skype: pajamadesign
Yahoo: jacobsingh
AIM: jacobsingh
gTalk: jacobsingh@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Changing the hostname jmeter-server reports to the client
Posted by sebb <se...@gmail.com>.
On 24/09/2008, Jacob Singh <ja...@gmail.com> wrote:
> Hello,
>
> I'm trying to get distributed search working on ec2 (if anyone has any
> results here, would love to hear them). Here's what I've got going:
>
> The public IP is 75.101.209.34
> and the private IP is 10.252.162.18
>
> ----
> jmeter log
> ----
>
> My client can connect when the server is running, and I can telnet in,
> but then has an issue here:
> 2008/09/24 08:55:40 INFO - jmeter.samplers.StandardSampleSender:
> Using Standard Remote Sampler for this test run
> 2008/09/24 08:58:49 ERROR - jmeter.engine.ClientJMeterEngine:
> java.rmi.ConnectException: Connection refused to host: 10.252.162.18;
> nested exception is:
> java.net.ConnectException: Connection timed out
>
> ------------------------------------
>
> Obviously, the server is sending the wrong IP address to the client.
>
Agreed.
> As you can see below, I am setting the rmi.server.hostname property
> and it is taking effect, however jmeter stubbornly refuses to actually
> treat this as its IP...
>
> ----
> jmeter-server log
> ----
>
> 2008/09/24 00:34:50 INFO - jmeter.JMeter: Setting System property:
> java.rmi.server.hostname=75.101.209.34
> 2008/09/24 00:34:50 INFO - jmeter.JMeter: Setting System property:
> server_port=1099
> 2008/09/24 00:34:50 INFO - jmeter.JMeter: Copyright (c) 1998-2008 The
> Apache Software Foundation
> 2008/09/24 00:34:50 INFO - jmeter.JMeter: Version 2.3.2 r665936
> 2008/09/24 00:34:50 INFO - jmeter.JMeter: java.version=1.6.0_04
> 2008/09/24 00:34:50 INFO - jmeter.JMeter: java.vm.name=Java
> HotSpot(TM) Server VM
> 2008/09/24 00:34:50 INFO - jmeter.JMeter: os.name=Linux
> 2008/09/24 00:34:50 INFO - jmeter.JMeter: os.arch=i386
> 2008/09/24 00:34:50 INFO - jmeter.JMeter: os.version=2.6.18-xenU-ec2-v1.0
> 2008/09/24 00:34:50 INFO - jmeter.JMeter: file.encoding=UTF-8
> 2008/09/24 00:34:50 INFO - jmeter.JMeter: Default Locale=English
> (United States)
> 2008/09/24 00:34:50 INFO - jmeter.JMeter: JMeter Locale=English
> (United States)
> 2008/09/24 00:34:50 INFO - jmeter.JMeter:
> JMeterHome=/usr/local/jakarta-jmeter-2.3.2
> 2008/09/24 00:34:50 INFO - jmeter.JMeter: user.dir
> =/usr/local/jakarta-jmeter-2.3.2
> 2008/09/24 00:34:50 INFO - jmeter.JMeter: PWD
> =/usr/local/jakarta-jmeter-2.3.2
> 2008/09/24 00:34:50 INFO - jmeter.JMeter: IP: 10.252.162.18 Name:
> domU-12-31-38-00-9D-E4.compute-1.internal FullName:
> domU-12-31-38-00-9D-E4.compute-1.internal
The above is just logging what InetAddress.getLocalHost() returns.
> 2008/09/24 00:34:51 INFO - jmeter.engine.RemoteJMeterEngineImpl:
> Starting backing engine on 1099
> 2008/09/24 00:34:51 INFO - jmeter.engine.RemoteJMeterEngineImpl: IP
> address=10.252.162.18
>
That just records the same as above.
The hostname gets passed to the JMeter engine, but is not then used for RMI.
> -------------------------
>
> I think one of the issues is that ec2 doesn't actually know that this
> is its ip because it is obviously behind a router. So even if you
> ping its public DNS, it will return the private domain.
> Can someone throw me a bone here? I've spent about 6hrs trying to fix
> this, and I'm very sad because this will be awesome when it is working
> :) I also plan to release an AMI at some point in the future.
>
Can you get a simple EchoClient/Server working on that setup?
Maybe that would give some pointers as to how to fix JMeter - e.g.
perhaps the RMI server needs to be run on the host given by the
rmi.server.hostname property.
At present the property is not directly used by JMeter - it was
assumed that the Java RMI would know what to do when the property is
defined. Indeed that's what the documentation suggests here:
http://java.sun.com/docs/books/tutorial/rmi/running.html
>
> --
>
> +1 510 277-0891 (o)
> +91 9999 33 7458 (m)
>
> web: http://pajamadesign.com
>
> Skype: pajamadesign
> Yahoo: jacobsingh
> AIM: jacobsingh
> gTalk: jacobsingh@gmail.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