jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Lin <wool...@gmail.com>
Subject Re: can't run jmeter 2.0.2 remotely on SuSE 9.X
Date Sat, 26 Feb 2005 00:36:03 GMT
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 <sergey@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


Mime
View raw message