You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Alexander Banthien <al...@questech.de> on 2003/07/17 11:22:16 UTC
Jmeter remote
Hello,
I have been trying to set up a stress test environment for a web
application. I am almost there using JMeter.
Unfortunately I did not manage to connect to a remote server (Linux, Sun
1.4.1_02), which was not within my LAN. I was using 1.8.1 and 1.9.RC3.
I did manage to connect to and use a neighboring server (Client and
server Win NT, Sun JDK 1.4.1_02). (To be honest: I do see some activity
of rmiregistry on the remote server, maybe it is connecting, but I don't
understand the log: see below)
People might want to note, that whitespaces in the installation path of
(at least) the Jmeter client broke the connectivity to the JMeter server
altogether.
Where the IP of the remote JMeter server is something official I get the
following error message on the client. The server records no connect at
all:
======================================
07/17/2003 11:13:33 AM INFO - jmeter.JMeter: Version 1.9.RC3
07/17/2003 11:14:45 AM INFO - jmeter.gui.action.Load: Loading file:
C:\WINNT\Profiles\Administrator\Desktop\ParentPay Users.jmx
07/17/2003 11:15:18 AM ERROR - jmeter.engine.ClientJMeterEngine:
java.rmi.ConnectException: Connection refused to host: 127.0.0.2; nested
exception is:
java.net.ConnectException: Connection refused: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
...
...
======================================
07/17/2003 11:15:18 AM WARN - jmeter.engine.ClientJMeterEngine: about
to run remote test
07/17/2003 11:15:19 AM WARN - jmeter.engine.ClientJMeterEngine: done
initiating run command
07/17/2003 11:15:19 AM WARN - jmeter.engine.ClientJMeterEngine: running
clientengine run method
07/17/2003 11:15:19 AM INFO - jmeter.engine: num threads = 5
07/17/2003 11:15:21 AM INFO - jmeter.engine: num threads = 5
07/17/2003 11:15:22 AM ERROR - jmeter.engine.ClientJMeterEngine:
java.rmi.ConnectException: Connection refused to host: 127.0.0.2; nested
exception is:
java.net.ConnectException: Connection refused: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
--
Mit freundlichen Grüßen
Alexander Banthien
_______________________________________
Alexander Banthien
Software Consulting
Fon: +49 (0)7661 90 35-15
Mob. +49 (0)173 9287388
Fax: +49 (0)7661 90 35-20
_______________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Jmeter remote (one step further?)
Posted by ms...@apache.org.
How does your test run when you run only on the client?
-Mike
On 17 Jul 2003 at 12:01, Alexander Banthien wrote:
> Hi once again,
>
> sorry about the noise, but I did achieve another step: The quoted problem
> was due to an entry in my /etc/hosts assigning 127.0.0.2 a name. I
commented
> that out. Now I don't receive error messages any longer:
>
> client log:
> =============================0
>
> 07/17/2003 11:56:54 AM WARN - jmeter.engine.ClientJMeterEngine: about
to
> run remote test
> 07/17/2003 11:56:54 AM WARN - jmeter.engine.ClientJMeterEngine: done
> initiating run command
> 07/17/2003 11:56:54 AM WARN - jmeter.engine.ClientJMeterEngine:
running
> clientengine run method
> 07/17/2003 11:56:54 AM INFO - jmeter.engine: num threads = 5
> 07/17/2003 11:56:54 AM INFO - jmeter.engine: num threads = 5
> 07/17/2003 11:56:55 AM WARN - jmeter.engine.ClientJMeterEngine: sent
host
> info
> ==============================
> server log:
> ==============================
> 07/17/2003 11:23:48 AM INFO - jmeter.JMeter: Version 1.9.RC3
> 07/17/2003 11:24:14 AM WARN - jmeter.engine: received host
> 07/17/2003 11:27:26 AM WARN - jmeter.engine: received test tree
> 07/17/2003 11:41:40 AM WARN - jmeter.engine: received host
> ==============================
>
> But after brief activity all java processes die away on the server and the
> tests don't run.
>
> Note that it was helpful to start the rmiregistry like so:
> rmiregistry -J-D:java.rmi.server.hostname=www.banthien.net &
>
> (probably becasue that machine has a plentitude of names and I wish to
use
> this one. It is declared in client and server hosts files)
>
> Any help greatly appreciated
>
> Alex
>
>
> Alexander Banthien wrote:
>
> > Hello,
> >
> > I have been trying to set up a stress test environment for a web
> > application. I am almost there using JMeter.
> >
> > Unfortunately I did not manage to connect to a remote server (Linux, Sun
> > 1.4.1_02), which was not within my LAN. I was using 1.8.1 and 1.9.RC3.
> >
> > I did manage to connect to and use a neighboring server (Client and
> > server Win NT, Sun JDK 1.4.1_02). (To be honest: I do see some activity
> > of rmiregistry on the remote server, maybe it is connecting, but I don't
> > understand the log: see below)
> >
> > People might want to note, that whitespaces in the installation path of
> > (at least) the Jmeter client broke the connectivity to the JMeter server
> > altogether.
> >
> > Where the IP of the remote JMeter server is something official I get the
> > following error message on the client. The server records no connect at
> > all:
> >
> > ======================================
> > 07/17/2003 11:13:33 AM INFO - jmeter.JMeter: Version 1.9.RC3
> > 07/17/2003 11:14:45 AM INFO - jmeter.gui.action.Load: Loading file:
> > C:\WINNT\Profiles\Administrator\Desktop\ParentPay Users.jmx
> > 07/17/2003 11:15:18 AM ERROR - jmeter.engine.ClientJMeterEngine:
> > java.rmi.ConnectException: Connection refused to host: 127.0.0.2; nested
> > exception is:
> > java.net.ConnectException: Connection refused: connect
> > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
> > at
> >
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
> > at
sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
> > ...
> > ...
> >
> > ======================================
> > 07/17/2003 11:15:18 AM WARN - jmeter.engine.ClientJMeterEngine:
about
> > to run remote test
> > 07/17/2003 11:15:19 AM WARN - jmeter.engine.ClientJMeterEngine:
done
> > initiating run command
> > 07/17/2003 11:15:19 AM WARN - jmeter.engine.ClientJMeterEngine:
running
> > clientengine run method
> > 07/17/2003 11:15:19 AM INFO - jmeter.engine: num threads = 5
> > 07/17/2003 11:15:21 AM INFO - jmeter.engine: num threads = 5
> > 07/17/2003 11:15:22 AM ERROR - jmeter.engine.ClientJMeterEngine:
> > java.rmi.ConnectException: Connection refused to host: 127.0.0.2; nested
> > exception is:
> > java.net.ConnectException: Connection refused: connect
> > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
> > at
> >
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
> > at
sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
> >
> > --
> >
> > Mit freundlichen Grüßen
> > Alexander Banthien
> >
> > _______________________________________
> > Alexander Banthien
> > Software Consulting
> >
> > Fon: +49 (0)7661 90 35-15
> > Mob. +49 (0)173 9287388
> > Fax: +49 (0)7661 90 35-20
> >
> > _______________________________________
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
> --
>
> Mit freundlichen Grüßen
> Alexander Banthien
>
> _______________________________________
> Alexander Banthien
> Software Consulting
>
> Fon: +49 (0)7661 90 35-15
> Mob. +49 (0)173 9287388
> Fax: +49 (0)7661 90 35-20
>
> _______________________________________
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
--
Michael Stover
mstover1@apache.org
Yahoo IM: mstover_ya
ICQ: 152975688
AIM: mstover777
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Jmeter remote (one step further?)
Posted by Alexander Banthien <al...@questech.de>.
Hi once again,
sorry about the noise, but I did achieve another step: The quoted problem
was due to an entry in my /etc/hosts assigning 127.0.0.2 a name. I commented
that out. Now I don't receive error messages any longer:
client log:
=============================0
07/17/2003 11:56:54 AM WARN - jmeter.engine.ClientJMeterEngine: about to
run remote test
07/17/2003 11:56:54 AM WARN - jmeter.engine.ClientJMeterEngine: done
initiating run command
07/17/2003 11:56:54 AM WARN - jmeter.engine.ClientJMeterEngine: running
clientengine run method
07/17/2003 11:56:54 AM INFO - jmeter.engine: num threads = 5
07/17/2003 11:56:54 AM INFO - jmeter.engine: num threads = 5
07/17/2003 11:56:55 AM WARN - jmeter.engine.ClientJMeterEngine: sent host
info
==============================
server log:
==============================
07/17/2003 11:23:48 AM INFO - jmeter.JMeter: Version 1.9.RC3
07/17/2003 11:24:14 AM WARN - jmeter.engine: received host
07/17/2003 11:27:26 AM WARN - jmeter.engine: received test tree
07/17/2003 11:41:40 AM WARN - jmeter.engine: received host
==============================
But after brief activity all java processes die away on the server and the
tests don't run.
Note that it was helpful to start the rmiregistry like so:
rmiregistry -J-D:java.rmi.server.hostname=www.banthien.net &
(probably becasue that machine has a plentitude of names and I wish to use
this one. It is declared in client and server hosts files)
Any help greatly appreciated
Alex
Alexander Banthien wrote:
> Hello,
>
> I have been trying to set up a stress test environment for a web
> application. I am almost there using JMeter.
>
> Unfortunately I did not manage to connect to a remote server (Linux, Sun
> 1.4.1_02), which was not within my LAN. I was using 1.8.1 and 1.9.RC3.
>
> I did manage to connect to and use a neighboring server (Client and
> server Win NT, Sun JDK 1.4.1_02). (To be honest: I do see some activity
> of rmiregistry on the remote server, maybe it is connecting, but I don't
> understand the log: see below)
>
> People might want to note, that whitespaces in the installation path of
> (at least) the Jmeter client broke the connectivity to the JMeter server
> altogether.
>
> Where the IP of the remote JMeter server is something official I get the
> following error message on the client. The server records no connect at
> all:
>
> ======================================
> 07/17/2003 11:13:33 AM INFO - jmeter.JMeter: Version 1.9.RC3
> 07/17/2003 11:14:45 AM INFO - jmeter.gui.action.Load: Loading file:
> C:\WINNT\Profiles\Administrator\Desktop\ParentPay Users.jmx
> 07/17/2003 11:15:18 AM ERROR - jmeter.engine.ClientJMeterEngine:
> java.rmi.ConnectException: Connection refused to host: 127.0.0.2; nested
> exception is:
> java.net.ConnectException: Connection refused: connect
> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
> at
> sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
> at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
> ...
> ...
>
> ======================================
> 07/17/2003 11:15:18 AM WARN - jmeter.engine.ClientJMeterEngine: about
> to run remote test
> 07/17/2003 11:15:19 AM WARN - jmeter.engine.ClientJMeterEngine: done
> initiating run command
> 07/17/2003 11:15:19 AM WARN - jmeter.engine.ClientJMeterEngine: running
> clientengine run method
> 07/17/2003 11:15:19 AM INFO - jmeter.engine: num threads = 5
> 07/17/2003 11:15:21 AM INFO - jmeter.engine: num threads = 5
> 07/17/2003 11:15:22 AM ERROR - jmeter.engine.ClientJMeterEngine:
> java.rmi.ConnectException: Connection refused to host: 127.0.0.2; nested
> exception is:
> java.net.ConnectException: Connection refused: connect
> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
> at
> sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
> at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
>
> --
>
> Mit freundlichen Grüßen
> Alexander Banthien
>
> _______________________________________
> Alexander Banthien
> Software Consulting
>
> Fon: +49 (0)7661 90 35-15
> Mob. +49 (0)173 9287388
> Fax: +49 (0)7661 90 35-20
>
> _______________________________________
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
--
Mit freundlichen Grüßen
Alexander Banthien
_______________________________________
Alexander Banthien
Software Consulting
Fon: +49 (0)7661 90 35-15
Mob. +49 (0)173 9287388
Fax: +49 (0)7661 90 35-20
_______________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Jmeter remote
Posted by Alexander Banthien <al...@questech.de>.
Hi Mike,
thanks for the help. port 1099 is open. But NAT seems to be the problem, if I
understand the bits right which I found in the web.
The problem: RMI puts the client address (10.10.10.21 in my case) into the payload
of the RMI packets, not just the TCP/IP headers. So my requests do reach the
server (TCP/IP wise) but the server will try and find 10.10.10.21 which he can't,
clearly. (I believe a second network connection is built in the reverse direction
up for callbacks)
I have given up. It is a pity. I couldn't even find a description on how to tunnel
it (e.g. ssh). Bad luck.
Thanks anyways, Alexander
mstover1@apache.org wrote:
> Any firewall between the two will block RMI. You'd have to open the RMI
> ports in your firewall (you'd have to look up what they are - 1099 at a guess,
> but I don't really remember).
>
> -Mike
>
> On 17 Jul 2003 at 13:25, Alexander Banthien wrote:
>
> > Hi,
> >
> > am I rightin thinking, that the JMeter client cannot sit behind a NAT
> > (straight forward) firewall if the server sits somewhere on the internet due
> > to the use of RMI?
> >
> > can RMI over HTTP be done? just guessing.
> >
> > Thanks anyway,
> >
> > Alexander
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
>
> --
> Michael Stover
> mstover1@apache.org
> Yahoo IM: mstover_ya
> ICQ: 152975688
> AIM: mstover777
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
--
Mit freundlichen Grüßen
Alexander Banthien
_______________________________________
Alexander Banthien
Software Consulting
Fon: +49 (0)7661 90 35-15
Mob. +49 (0)173 9287388
Fax: +49 (0)7661 90 35-20
_______________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Jmeter remote
Posted by ms...@apache.org.
Any firewall between the two will block RMI. You'd have to open the RMI
ports in your firewall (you'd have to look up what they are - 1099 at a guess,
but I don't really remember).
-Mike
On 17 Jul 2003 at 13:25, Alexander Banthien wrote:
> Hi,
>
> am I rightin thinking, that the JMeter client cannot sit behind a NAT
> (straight forward) firewall if the server sits somewhere on the internet due
> to the use of RMI?
>
> can RMI over HTTP be done? just guessing.
>
> Thanks anyway,
>
> Alexander
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
--
Michael Stover
mstover1@apache.org
Yahoo IM: mstover_ya
ICQ: 152975688
AIM: mstover777
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Jmeter remote
Posted by Alexander Banthien <al...@questech.de>.
Hi,
am I rightin thinking, that the JMeter client cannot sit behind a NAT
(straight forward) firewall if the server sits somewhere on the internet due
to the use of RMI?
can RMI over HTTP be done? just guessing.
Thanks anyway,
Alexander
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org