You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Sergey Ten <se...@sourcelabs.com> on 2005/02/25 23:31:45 UTC
Re: can't run jmeter 2.0.2 remotely on SuSE 9.X
I found a good article about rmiregistry
(http://www.developer.com/java/ent/article.php/10933_3455311_3), which
helped me out to solve the mistery with 127.0.0.2. Both computers were
protected by firewalls, with only few ports (including 1099) opened up.
After I opened all ports above 1024, I could move a bit further: now my
client sees 192.168.0.16, but for some reason can't remotely execute a
test. I enabled logging on both ends, and don't see anything suspicious.
jmeter.log on the client box has the following information:
2005/02/25 14:24:40 INFO - jmeter.engine.ClientJMeterEngine: about to
run remote test
2005/02/25 14:24:40 INFO - jmeter.engine.ClientJMeterEngine: done
initiating run command
2005/02/25 14:24:40 INFO - jmeter.engine.ClientJMeterEngine: running
clientengine run method
2005/02/25 14:24:40 INFO - jmeter.engine.ConvertListeners: num threads
= 10
2005/02/25 14:24:40 INFO - jmeter.engine.ConvertListeners: num threads
= 10
2005/02/25 14:24:40 INFO - jmeter.engine.ClientJMeterEngine: sent host
=<server_name><domain_name>
2005/02/25 14:24:40 INFO - jmeter.engine.ClientJMeterEngine: sent test
2005/02/25 14:24:40 INFO - jmeter.engine.ClientJMeterEngine: sent run
command
Can someone shed light on what can be wrong?
Thanks,
Sergey
Sergey Ten wrote:
> Hello all,
>
> I am trying to run JMeter 2.0.2 remotely using two boxes with SuSE 9.X
> installed on both machines.
> Those machines are on the same switch box, and their IP addresses are
> 192.168.0.12 and 192.168.0.16.
>
> On 192.168.0.16 rmiregistry was called as follows:
> rmiregistry -J-D:java.rmi.server.hostname=192.168.0.16
> -J-D:java.security.policy=`dirname $0`/java.policy&.
> Java.policy file contains the following lines:
> permission java.net.SocketPermission "*:1024-65535","connect,accept";
> permission java.net.SocketPermission "*:80","connect";
> permission java.security.AllPermission;
>
> Netstat shows that rmiregistry is listening to port 1099.
>
> On 192.168.0.16 I could successfully run an httprequest test using
> RemoteStart (both the client abd the server are running on the same
> box, but instead of 127.0.0.1 I am using 192.168.0.16 IP address to
> identify the server).
> But when I tried to run the same httprequest test on 192.168.0.12 (and
> the server was still running on 192.168.0.16) I got the following error:
>
> 2005/02/22 16:28:37 ERROR - jmeter.engine.ClientJMeterEngine:
> java.rmi.ConnectException: Connection refused to host: 127.0.0.2;
>
> I found one email which reported about the same problem (attempt to
> talk to 127.0.0.2), but my situation is somewhat different: even after
> I commented out the line with 127.0.0.2 in the /etc/hosts file and
> rebooted the machine, I am still getting the same error mesage (see
> attached jmeter.err file).
>
> I am trying to run jmeter remotely for almost a whole day, and did not
> succeed yet. I even replaced 127.0.0.1 with 192.168.0.16 in the
> /etc/hosts file on 192.168.0.16, but see no difference at all. I am
> not sure where this 127.0.0.2 is coming from. Any help will be
> appreciated.
>
> Thanks,
> Sergey
>
>------------------------------------------------------------------------
>
>#!/bin/sh
>
>## $Id: jmeter-server,v 1.11 2004/02/16 13:34:10 sebb Exp $
>## Copyright 2001-2004 The Apache Software Foundation
>##
>## Licensed under the Apache License, Version 2.0 (the "License");
>## you may not use this file except in compliance with the License.
>## You may obtain a copy of the License at
>##
>## http://www.apache.org/licenses/LICENSE-2.0
>##
>## Unless required by applicable law or agreed to in writing, software
>## distributed under the License is distributed on an "AS IS" BASIS,
>## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>## See the License for the specific language governing permissions and
>## limitations under the License.
>
>set OLDCLASSPATH=$CLASSPATH
>export OLDCLASSPATH
>set CLASSPATH=`dirname $0`/../lib/ext/ApacheJMeter_core.jar:`dirname $0`/../lib/jorphan.jar:`dirname $0`/../lib/logkit-1.2.jar
>export CLASSPATH
>rmiregistry -J-D:java.rmi.server.hostname=192.168.0.16 -J-D:java.security.policy=`dirname $0`/java.policy&
>set CLASSPATH=$OLDCLASSPATH
>export CLASSPATH
># java -jar `dirname $0`/ApacheJMeter.jar -Djava.rmi.server.hostname=192.168.0.16 -Djava.security.policy=`dirname $0`/java.policy -s "$@"
>java -jar `dirname $0`/ApacheJMeter.jar -s "$@"
>
>------------------------------------------------------------------------
>
>2005/02/22 16:28:16 INFO - jmeter.JMeter: Setting System property: java.security.policy=java.policy
>2005/02/22 16:28:16 INFO - jmeter.JMeter: Version 2.0.2
>2005/02/22 16:28:16 INFO - jmeter.JMeter: java.version=1.4.2
>2005/02/22 16:28:16 INFO - jmeter.JMeter: Copyright (c) 1998-2004 The Apache Software Foundation
>2005/02/22 16:28:24 INFO - jmeter.gui.action.Load: Loading file: /home/willpugh/jakarta-jmeter-2.0.2/bin/Aggregate Report.jmx
>2005/02/22 16:28:37 ERROR - jmeter.engine.ClientJMeterEngine: java.rmi.ConnectException: Connection refused to host: 127.0.0.2; nested exception is:
> java.net.ConnectException: Connection refused
> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:585)
> at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:203)
> at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:189)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:117)
> at org.apache.jmeter.engine.RemoteJMeterEngineImpl_Stub.reset(Unknown Source)
> at org.apache.jmeter.engine.ClientJMeterEngine.reset(ClientJMeterEngine.java:95)
> at org.apache.jmeter.gui.action.RemoteStart.doRemoteStart(RemoteStart.java:181)
> at org.apache.jmeter.gui.action.RemoteStart.doAction(RemoteStart.java:79)
> at org.apache.jmeter.gui.action.ActionRouter.performAction(ActionRouter.java:81)
> at org.apache.jmeter.gui.action.ActionRouter.access$000(ActionRouter.java:44)
> at org.apache.jmeter.gui.action.ActionRouter$1.run(ActionRouter.java:62)
> at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java(Compiled Code))
> at java.awt.EventQueue.dispatchEvent(EventQueue.java(Compiled Code))
> at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java(Compiled Code))
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java(Compiled Code))
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:181)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:173)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:136)
>Caused by: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:331)
> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:196)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:183)
> at java.net.Socket.connect(Socket.java:478)
> at java.net.Socket.connect(Socket.java:428)
> at java.net.Socket.<init>(Socket.java:335)
> at java.net.Socket.<init>(Socket.java:150)
> at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
> at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:144)
> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:580)
> ... 17 more
>
>2005/02/22 16:28:37 INFO - jmeter.engine.ClientJMeterEngine: about to run remote test
>2005/02/22 16:28:37 INFO - jmeter.engine.ClientJMeterEngine: done initiating run command
>2005/02/22 16:28:37 INFO - jmeter.engine.ClientJMeterEngine: running clientengine run method
>2005/02/22 16:28:37 INFO - jmeter.engine.ConvertListeners: num threads = 100
>2005/02/22 16:28:37 INFO - jmeter.engine.ConvertListeners: num threads = 100
>2005/02/22 16:28:37 ERROR - jmeter.engine.ClientJMeterEngine: java.rmi.ConnectException: Connection refused to host: 127.0.0.2; nested exception is:
> java.net.ConnectException: Connection refused
> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:585)
> at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:203)
> at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:189)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:117)
> at org.apache.jmeter.engine.RemoteJMeterEngineImpl_Stub.setHost(Unknown Source)
> at org.apache.jmeter.engine.ClientJMeterEngine.run(ClientJMeterEngine.java:124)
> at java.lang.Thread.run(Thread.java:567)
>Caused by: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:331)
> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:196)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:183)
> at java.net.Socket.connect(Socket.java:478)
> at java.net.Socket.connect(Socket.java:428)
> at java.net.Socket.<init>(Socket.java:335)
> at java.net.Socket.<init>(Socket.java:150)
> at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
> at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:144)
> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:580)
> ... 6 more
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: can't run jmeter 2.0.2 remotely on SuSE 9.X
Posted by Sergey Ten <se...@sourcelabs.com>.
I passed your hi to Will and he passed his hi back to you.
Sergey
Peter Lin wrote:
>by the way, say hi to will for me
>
>peter
>
>---------------------------------------------------------------------
>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: can't run jmeter 2.0.2 remotely on SuSE 9.X
Posted by Peter Lin <wo...@gmail.com>.
by the way, say hi to will for me
peter
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: can't run jmeter 2.0.2 remotely on SuSE 9.X
Posted by Peter Lin <wo...@gmail.com>.
after I sent the message I remember you're using Suse.
what i would do is run netstat and see if a connection is being made
by jmeter. if it isn't, my guess is something else is blocking the
traffic. you should definitely see the a connection between the jmeter
server and client. I usually run a command like
netstat -p tcp | grep HTTP
netstat -p tcp | grep <the_ip>
peter
On Fri, 25 Feb 2005 15:43:46 -0800, Sergey Ten <se...@sourcelabs.com> wrote:
> Thank you for your reply, Peter. Turns out the 127.0.0.2 problem was
> caused by firewalls: each of the computers was protected by its own
> firewall, with only few ports opened for access. I assumed that
> jmeter (client and server) would use 1099 (default rmiregistry) port.
> This assumption turned to be wrong. After I disabled the firewalls, I no
> longer see 127.0.0.2-related errors. However, I am still seeing the
> following error messages in jmeter.log on the server:
>
> java.rmi.ConnectException: Connection refused to host: 192.168.0.16;
> nested exception is:
> java.net.ConnectException: Connection refused
> 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)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:101)
> at
> org.apache.jmeter.samplers.RemoteSampleListenerImpl_Stub.testStarted(Unknown
> Source)
> at
> org.apache.jmeter.samplers.RemoteListenerWrapper.testStarted(RemoteListenerWrapper.java:113)
> at
> org.apache.jmeter.engine.StandardJMeterEngine.notifyTestListenersOfStart(StandardJMeterEngine.java:224)
> at
> org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:354)
> at java.lang.Thread.run(Thread.java:534)
> Caused by: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
> at java.net.Socket.connect(Socket.java:452)
> at java.net.Socket.connect(Socket.java:402)
> at java.net.Socket.<init>(Socket.java:309)
> at java.net.Socket.<init>(Socket.java:124)
> at
> sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
> at
> sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
> ... 8 more
>
> Sergey
>
>
> Peter Lin wrote:
>
> >by any chance are the two systems on different subnets?
> >
> >for distributed testing to work, the systems must be on the same
> >subnet, otherwise RMI will not be able to connect.
> >
> >
> >peter
> >
> >---------------------------------------------------------------------
> >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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: can't run jmeter 2.0.2 remotely on SuSE 9.X
Posted by Peter Lin <wo...@gmail.com>.
great. I'll add this to the wiki and docs when I get home tonight.
thanks
peter
On Mon, 28 Feb 2005 09:05:56 -0800, Sergey Ten <se...@sourcelabs.com> wrote:
> Peter,
>
> Here is what I have found:
>
> 1. Each computer was protected by a firewall, which caused the problem.
> 2. Unfortunately, the problem was reported in a form which mislead
> me. Since I invoked rmiregistry with the following debug options
> rmiregistry -J-Dsun.rmi.log.debug=true
> -J-Dsun.rmi.server.exceptionTrace=true
> -J-Dsun.rmi.loader.logLevel=verbose
> -J-Dsun.rmi.dgc.logLevel=verbose
> -J-Dsun.rmi.transport.logLevel=verbose
> -J-Dsun.rmi.transport.tcp.logLevel=verbose
> I got reports about refused connections to 127.0.0.2. Searching
> the internet, I found few suggestions to remove loopbacks
> 127.0.0.1 and 127.0.0.2 from etc/hosts. Turns out that
> jmeter-server can't connect to rmiregistry if 127.0.0.2 loopback
> is not available.
> The real fix is to replace the following line in jmeter-server:
>
> `dirname $0`/jmeter -s "$@"
>
> with
>
> HOST="-Djava.rmi.server.hostname=<computer_name><computer_domain>
> -Djava.security.policy=`dirname $0`/<policy_file>"
> `dirname $0`/jmeter $HOST -s "$@"
>
> create a policy file and add <computer_name><computer_domain> line
> to /etc/hosts
>
> Hope this will help.
>
> Sergey
>
> Peter Lin wrote:
>
> >yeah I am interested. I'll try to add it to our docs :)
> >
> >peter
> >
> >
> >On Fri, 25 Feb 2005 17:23:54 -0800, Sergey Ten <se...@sourcelabs.com> wrote:
> >
> >
> >>Thank you Peter for your help. I fixed the problem although am not sure
> >>why it works. I would like to go home and think about it a bit more. I
> >>will share my findings with you if you are interested (perhaps you are not).
> >>
> >>Thank you again for your help,
> >>Sergey
> >>
> >>Peter Lin wrote:
> >>
> >>
> >>
> >>>hmm... so something is causing the connections to go into time_wait.
> >>>
> >>>it should be "established" or "listen", depending on whether it's the
> >>>server or client. time_wait doesn't seem right to me. on the server
> >>>you should see the RMI server running.
> >>>
> >>>when you "netstat -ta" you should see this on the system running jmeter server.
> >>>
> >>>tcp 0 0 *:1099 *:* LISTEN
> >>>
> >>>peter
> >>>
> >>>
> >>>On Fri, 25 Feb 2005 17:01:39 -0800, Sergey Ten <se...@sourcelabs.com> wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>I ran the command and it showed that the connection was established at
> >>>>21771 and 4432 ports. The status of the connection is TIME_WAIT.
> >>>>
> >>>>Sergey
> >>>>
> >>>>Peter Lin wrote:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>duhh wrong netstat option
> >>>>>
> >>>>>
> >>>>>netstat -ta | grep <ip>
> >>>>>
> >>>>>that should show all tcp connections. hope that helps
> >>>>>
> >>>>>peter
> >>>>>
> >>>>>---------------------------------------------------------------------
> >>>>>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
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>---------------------------------------------------------------------
> >>>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
> >>
> >>
> >>
> >>
> >
> >---------------------------------------------------------------------
> >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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Fwd: can't run jmeter 2.0.2 remotely on SuSE 9.X
Posted by Peter Lin <wo...@gmail.com>.
I plan to add this information provided by Sergey of sourcelabs to the
docs tonight. just an FYI
peter
---------- Forwarded message ----------
From: Sergey Ten <se...@sourcelabs.com>
Date: Mon, 28 Feb 2005 09:05:56 -0800
Subject: Re: can't run jmeter 2.0.2 remotely on SuSE 9.X
To: JMeter Users List <jm...@jakarta.apache.org>
Peter,
Here is what I have found:
1. Each computer was protected by a firewall, which caused the problem.
2. Unfortunately, the problem was reported in a form which mislead
me. Since I invoked rmiregistry with the following debug options
rmiregistry -J-Dsun.rmi.log.debug=true
-J-Dsun.rmi.server.exceptionTrace=true
-J-Dsun.rmi.loader.logLevel=verbose
-J-Dsun.rmi.dgc.logLevel=verbose
-J-Dsun.rmi.transport.logLevel=verbose
-J-Dsun.rmi.transport.tcp.logLevel=verbose
I got reports about refused connections to 127.0.0.2. Searching
the internet, I found few suggestions to remove loopbacks
127.0.0.1 and 127.0.0.2 from etc/hosts. Turns out that
jmeter-server can't connect to rmiregistry if 127.0.0.2 loopback
is not available.
The real fix is to replace the following line in jmeter-server:
`dirname $0`/jmeter -s "$@"
with
HOST="-Djava.rmi.server.hostname=<computer_name><computer_domain>
-Djava.security.policy=`dirname $0`/<policy_file>"
`dirname $0`/jmeter $HOST -s "$@"
create a policy file and add <computer_name><computer_domain> line
to /etc/hosts
Hope this will help.
Sergey
Peter Lin wrote:
>yeah I am interested. I'll try to add it to our docs :)
>
>peter
>
>
>On Fri, 25 Feb 2005 17:23:54 -0800, Sergey Ten <se...@sourcelabs.com> wrote:
>
>
>>Thank you Peter for your help. I fixed the problem although am not sure
>>why it works. I would like to go home and think about it a bit more. I
>>will share my findings with you if you are interested (perhaps you are not).
>>
>>Thank you again for your help,
>>Sergey
>>
>>Peter Lin wrote:
>>
>>
>>
>>>hmm... so something is causing the connections to go into time_wait.
>>>
>>>it should be "established" or "listen", depending on whether it's the
>>>server or client. time_wait doesn't seem right to me. on the server
>>>you should see the RMI server running.
>>>
>>>when you "netstat -ta" you should see this on the system running
jmeter server.
>>>
>>>tcp 0 0 *:1099 *:* LISTEN
>>>
>>>peter
>>>
>>>
>>>On Fri, 25 Feb 2005 17:01:39 -0800, Sergey Ten <se...@sourcelabs.com> wrote:
>>>
>>>
>>>
>>>
>>>>I ran the command and it showed that the connection was established at
>>>>21771 and 4432 ports. The status of the connection is TIME_WAIT.
>>>>
>>>>Sergey
>>>>
>>>>Peter Lin wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>duhh wrong netstat option
>>>>>
>>>>>
>>>>>netstat -ta | grep <ip>
>>>>>
>>>>>that should show all tcp connections. hope that helps
>>>>>
>>>>>peter
>>>>>
>>>>>---------------------------------------------------------------------
>>>>>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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>---------------------------------------------------------------------
>>>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
>>
>>
>>
>>
>
>---------------------------------------------------------------------
>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
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: can't run jmeter 2.0.2 remotely on SuSE 9.X
Posted by Sergey Ten <se...@sourcelabs.com>.
Peter,
Here is what I have found:
1. Each computer was protected by a firewall, which caused the problem.
2. Unfortunately, the problem was reported in a form which mislead
me. Since I invoked rmiregistry with the following debug options
rmiregistry -J-Dsun.rmi.log.debug=true
-J-Dsun.rmi.server.exceptionTrace=true
-J-Dsun.rmi.loader.logLevel=verbose
-J-Dsun.rmi.dgc.logLevel=verbose
-J-Dsun.rmi.transport.logLevel=verbose
-J-Dsun.rmi.transport.tcp.logLevel=verbose
I got reports about refused connections to 127.0.0.2. Searching
the internet, I found few suggestions to remove loopbacks
127.0.0.1 and 127.0.0.2 from etc/hosts. Turns out that
jmeter-server can't connect to rmiregistry if 127.0.0.2 loopback
is not available.
The real fix is to replace the following line in jmeter-server:
`dirname $0`/jmeter -s "$@"
with
HOST="-Djava.rmi.server.hostname=<computer_name><computer_domain>
-Djava.security.policy=`dirname $0`/<policy_file>"
`dirname $0`/jmeter $HOST -s "$@"
create a policy file and add <computer_name><computer_domain> line
to /etc/hosts
Hope this will help.
Sergey
Peter Lin wrote:
>yeah I am interested. I'll try to add it to our docs :)
>
>peter
>
>
>On Fri, 25 Feb 2005 17:23:54 -0800, Sergey Ten <se...@sourcelabs.com> wrote:
>
>
>>Thank you Peter for your help. I fixed the problem although am not sure
>>why it works. I would like to go home and think about it a bit more. I
>>will share my findings with you if you are interested (perhaps you are not).
>>
>>Thank you again for your help,
>>Sergey
>>
>>Peter Lin wrote:
>>
>>
>>
>>>hmm... so something is causing the connections to go into time_wait.
>>>
>>>it should be "established" or "listen", depending on whether it's the
>>>server or client. time_wait doesn't seem right to me. on the server
>>>you should see the RMI server running.
>>>
>>>when you "netstat -ta" you should see this on the system running jmeter server.
>>>
>>>tcp 0 0 *:1099 *:* LISTEN
>>>
>>>peter
>>>
>>>
>>>On Fri, 25 Feb 2005 17:01:39 -0800, Sergey Ten <se...@sourcelabs.com> wrote:
>>>
>>>
>>>
>>>
>>>>I ran the command and it showed that the connection was established at
>>>>21771 and 4432 ports. The status of the connection is TIME_WAIT.
>>>>
>>>>Sergey
>>>>
>>>>Peter Lin wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>duhh wrong netstat option
>>>>>
>>>>>
>>>>>netstat -ta | grep <ip>
>>>>>
>>>>>that should show all tcp connections. hope that helps
>>>>>
>>>>>peter
>>>>>
>>>>>---------------------------------------------------------------------
>>>>>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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>---------------------------------------------------------------------
>>>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
>>
>>
>>
>>
>
>---------------------------------------------------------------------
>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: can't run jmeter 2.0.2 remotely on SuSE 9.X
Posted by Peter Lin <wo...@gmail.com>.
yeah I am interested. I'll try to add it to our docs :)
peter
On Fri, 25 Feb 2005 17:23:54 -0800, Sergey Ten <se...@sourcelabs.com> wrote:
> Thank you Peter for your help. I fixed the problem although am not sure
> why it works. I would like to go home and think about it a bit more. I
> will share my findings with you if you are interested (perhaps you are not).
>
> Thank you again for your help,
> Sergey
>
> Peter Lin wrote:
>
> >hmm... so something is causing the connections to go into time_wait.
> >
> >it should be "established" or "listen", depending on whether it's the
> >server or client. time_wait doesn't seem right to me. on the server
> >you should see the RMI server running.
> >
> >when you "netstat -ta" you should see this on the system running jmeter server.
> >
> >tcp 0 0 *:1099 *:* LISTEN
> >
> >peter
> >
> >
> >On Fri, 25 Feb 2005 17:01:39 -0800, Sergey Ten <se...@sourcelabs.com> wrote:
> >
> >
> >>I ran the command and it showed that the connection was established at
> >>21771 and 4432 ports. The status of the connection is TIME_WAIT.
> >>
> >>Sergey
> >>
> >>Peter Lin wrote:
> >>
> >>
> >>
> >>>duhh wrong netstat option
> >>>
> >>>
> >>>netstat -ta | grep <ip>
> >>>
> >>>that should show all tcp connections. hope that helps
> >>>
> >>>peter
> >>>
> >>>---------------------------------------------------------------------
> >>>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
> >>
> >>
> >>
> >>
> >
> >---------------------------------------------------------------------
> >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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: can't run jmeter 2.0.2 remotely on SuSE 9.X
Posted by Sergey Ten <se...@sourcelabs.com>.
Thank you Peter for your help. I fixed the problem although am not sure
why it works. I would like to go home and think about it a bit more. I
will share my findings with you if you are interested (perhaps you are not).
Thank you again for your help,
Sergey
Peter Lin wrote:
>hmm... so something is causing the connections to go into time_wait.
>
>it should be "established" or "listen", depending on whether it's the
>server or client. time_wait doesn't seem right to me. on the server
>you should see the RMI server running.
>
>when you "netstat -ta" you should see this on the system running jmeter server.
>
>tcp 0 0 *:1099 *:* LISTEN
>
>peter
>
>
>On Fri, 25 Feb 2005 17:01:39 -0800, Sergey Ten <se...@sourcelabs.com> wrote:
>
>
>>I ran the command and it showed that the connection was established at
>>21771 and 4432 ports. The status of the connection is TIME_WAIT.
>>
>>Sergey
>>
>>Peter Lin wrote:
>>
>>
>>
>>>duhh wrong netstat option
>>>
>>>
>>>netstat -ta | grep <ip>
>>>
>>>that should show all tcp connections. hope that helps
>>>
>>>peter
>>>
>>>---------------------------------------------------------------------
>>>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
>>
>>
>>
>>
>
>---------------------------------------------------------------------
>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: can't run jmeter 2.0.2 remotely on SuSE 9.X
Posted by Peter Lin <wo...@gmail.com>.
hmm... so something is causing the connections to go into time_wait.
it should be "established" or "listen", depending on whether it's the
server or client. time_wait doesn't seem right to me. on the server
you should see the RMI server running.
when you "netstat -ta" you should see this on the system running jmeter server.
tcp 0 0 *:1099 *:* LISTEN
peter
On Fri, 25 Feb 2005 17:01:39 -0800, Sergey Ten <se...@sourcelabs.com> wrote:
> I ran the command and it showed that the connection was established at
> 21771 and 4432 ports. The status of the connection is TIME_WAIT.
>
> Sergey
>
> Peter Lin wrote:
>
> >duhh wrong netstat option
> >
> >
> >netstat -ta | grep <ip>
> >
> >that should show all tcp connections. hope that helps
> >
> >peter
> >
> >---------------------------------------------------------------------
> >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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: can't run jmeter 2.0.2 remotely on SuSE 9.X
Posted by Sergey Ten <se...@sourcelabs.com>.
I ran the command and it showed that the connection was established at
21771 and 4432 ports. The status of the connection is TIME_WAIT.
Sergey
Peter Lin wrote:
>duhh wrong netstat option
>
>
>netstat -ta | grep <ip>
>
>that should show all tcp connections. hope that helps
>
>peter
>
>---------------------------------------------------------------------
>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: can't run jmeter 2.0.2 remotely on SuSE 9.X
Posted by Peter Lin <wo...@gmail.com>.
duhh wrong netstat option
netstat -ta | grep <ip>
that should show all tcp connections. hope that helps
peter
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: can't run jmeter 2.0.2 remotely on SuSE 9.X
Posted by Peter Lin <wo...@gmail.com>.
it would appear something is still blocking the traffic. do you have
windows firewall turned on? depending on which virus protection
software you use, it may not be really off :)
in some cases, you have to go to windows admin -> services and shut it
down that way.
peter
On Fri, 25 Feb 2005 15:43:46 -0800, Sergey Ten <se...@sourcelabs.com> wrote:
> Thank you for your reply, Peter. Turns out the 127.0.0.2 problem was
> caused by firewalls: each of the computers was protected by its own
> firewall, with only few ports opened for access. I assumed that
> jmeter (client and server) would use 1099 (default rmiregistry) port.
> This assumption turned to be wrong. After I disabled the firewalls, I no
> longer see 127.0.0.2-related errors. However, I am still seeing the
> following error messages in jmeter.log on the server:
>
> java.rmi.ConnectException: Connection refused to host: 192.168.0.16;
> nested exception is:
> java.net.ConnectException: Connection refused
> 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)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:101)
> at
> org.apache.jmeter.samplers.RemoteSampleListenerImpl_Stub.testStarted(Unknown
> Source)
> at
> org.apache.jmeter.samplers.RemoteListenerWrapper.testStarted(RemoteListenerWrapper.java:113)
> at
> org.apache.jmeter.engine.StandardJMeterEngine.notifyTestListenersOfStart(StandardJMeterEngine.java:224)
> at
> org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:354)
> at java.lang.Thread.run(Thread.java:534)
> Caused by: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
> at java.net.Socket.connect(Socket.java:452)
> at java.net.Socket.connect(Socket.java:402)
> at java.net.Socket.<init>(Socket.java:309)
> at java.net.Socket.<init>(Socket.java:124)
> at
> sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
> at
> sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
> ... 8 more
>
> Sergey
>
>
> Peter Lin wrote:
>
> >by any chance are the two systems on different subnets?
> >
> >for distributed testing to work, the systems must be on the same
> >subnet, otherwise RMI will not be able to connect.
> >
> >
> >peter
> >
> >---------------------------------------------------------------------
> >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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: can't run jmeter 2.0.2 remotely on SuSE 9.X
Posted by Sergey Ten <se...@sourcelabs.com>.
Thank you for your reply, Peter. Turns out the 127.0.0.2 problem was
caused by firewalls: each of the computers was protected by its own
firewall, with only few ports opened for access. I assumed that
jmeter (client and server) would use 1099 (default rmiregistry) port.
This assumption turned to be wrong. After I disabled the firewalls, I no
longer see 127.0.0.2-related errors. However, I am still seeing the
following error messages in jmeter.log on the server:
java.rmi.ConnectException: Connection refused to host: 192.168.0.16;
nested exception is:
java.net.ConnectException: Connection refused
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)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:101)
at
org.apache.jmeter.samplers.RemoteSampleListenerImpl_Stub.testStarted(Unknown
Source)
at
org.apache.jmeter.samplers.RemoteListenerWrapper.testStarted(RemoteListenerWrapper.java:113)
at
org.apache.jmeter.engine.StandardJMeterEngine.notifyTestListenersOfStart(StandardJMeterEngine.java:224)
at
org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:354)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at java.net.Socket.connect(Socket.java:402)
at java.net.Socket.<init>(Socket.java:309)
at java.net.Socket.<init>(Socket.java:124)
at
sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
at
sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
... 8 more
Sergey
Peter Lin wrote:
>by any chance are the two systems on different subnets?
>
>for distributed testing to work, the systems must be on the same
>subnet, otherwise RMI will not be able to connect.
>
>
>peter
>
>---------------------------------------------------------------------
>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: can't run jmeter 2.0.2 remotely on SuSE 9.X
Posted by Peter Lin <wo...@gmail.com>.
by any chance are the two systems on different subnets?
for distributed testing to work, the systems must be on the same
subnet, otherwise RMI will not be able to connect.
peter
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org