I have a WinXP <--> Redhat AS 3.0 remote test that works fine with JMeter 2.3.2.

I am starting the test from the GUI on my WinXP box via the Run -> Remote Start 
Menu and selecting the remote client I defined in the jmeter.properties file.

I would check the following:
1.  remote_hosts= property in the jmeters.properties file.
2.  Do a netstat -nap | grep 1099 and make sure the FC6 server is listen on the 
IP listed in the properties file
3.  Run wireshark/ethereal on the FC6 box and listen for requests coming from 
the WinXP.  
4.  Run wireshark/ethereal on the WinXP and listen for requests being sent to 
the FC6 box to port 1099.  If none, then JMeter or Java may be having a problem.

I suspect it is probably a networking problem but it could be something else.  
Do you have SELinux enabled?  

Jason





----- Original Message ----
From: Yaroslav <[EMAIL PROTECTED]>
To: [email protected]
Sent: Thursday, July 10, 2008 5:50:11 PM
Subject: Re: JMeter remote/distributed testing not working; No error message in 
log


Thx "sebb-2-2".

But regardless of anything - 
HELLO - PEOPLE: 
DOES SOMEBODY HAVE WORKING JMETER REMOTE TESTING ENVIRONMENT LIKE:
JMETER-CLIENT (WINXP) <-> JMETER-SERVER (LINUX FC6 OR RH4) ?????


sebb-2-2 wrote:
> 
> Sorry, in that case I'm out of ideas.
> 
> On 10/07/2008, Yaroslav <[EMAIL PROTECTED]> wrote:
>>
>>  Yes, I've checked that but did not provide in my reply.
>>  No problem to have access form my jmeter-client box (WinXP) to
>> jmeter-server
>>  box (Linux FC6) by  telnet. I have opening session by "telnet
>> 10.100.30.41
>>  1099".
>>
>>
>>
>>
>>  sebb-2-2 wrote:
>>  >
>>  > On 10/07/2008, Yaroslav <[EMAIL PROTECTED]> wrote:
>>  >>
>>  >>  Hi All,
>>  >>
>>  >>  I'm using jmeter 2.3.2.
>>  >>
>>  >>  Jmeter-client is running on WinXP and Jmeter-server on Linux (FC6).
>>  >>
>>  >>  In the same case as you described my client jmeter.log shows:
>>  >>
>>  >>  2008/07/10 11:41:57 ERROR - jmeter.engine.ClientJMeterEngine:
>>  >>  java.rmi.ConnectIOException: Exception creating connection to:
>>  >> 10.100.30.41;
>>  >>  nested exception is:
>>  >>        java.net.NoRouteToHostException: No route to host: connect
>>  >
>>  > That probably means the network is not set up correctly.
>>  >
>>  > Try
>>  >
>>  > telnet 10.100.30.41 1039
>>  >
>>  > from the client and you will see a similar error.
>>  >
>>  >>         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown
>> Source)
>>  >>         at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown
>>  >> Source)
>>  >>         at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown
>> Source)
>>  >>         at sun.rmi.server.UnicastRef.invoke(Unknown Source)
>>  >>
>>  >>         at
>>  >> org.apache.jmeter.engine.RemoteJMeterEngineImpl_Stub.setHost(Unknown
>>  >>  Source)
>>  >>         at
>>  >>
>>  >>
>> org.apache.jmeter.engine.ClientJMeterEngine.run(ClientJMeterEngine.java:126)
>>  >>         at java.lang.Thread.run(Unknown Source)
>>  >>  Caused by: java.net.NoRouteToHostException: No route to host:
>> connect
>>  >>
>>  >>         at java.net.PlainSocketImpl.socketConnect(Native Method)
>>  >>
>>  >>         at java.net.PlainSocketImpl.doConnect(Unknown Source)
>>  >>         at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
>>  >>         at java.net.PlainSocketImpl.connect(Unknown Source)
>>  >>         at java.net.SocksSocketImpl.connect(Unknown Source)
>>  >>         at java.net.Socket.connect(Unknown Source)
>>  >>         at java.net.Socket.connect(Unknown Source)
>>  >>         at java.net.Socket.<init>(Unknown Source)
>>  >>         at java.net.Socket.<init>(Unknown Source)
>>  >>         at
>>  >> sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown
>>  >>  Source)
>>  >>         at
>>  >> sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown
>>  >>  Source)
>>  >>         ... 7 more
>>  >>
>>  >>  where "10.100.30.41" where the IP is correct and points to
>> jmeter-server
>>  >>  side.
>>  >>
>>  >>  According to network firewall log - my client sent request to the
>>  >>  jmeter-server on port 1099.
>>  >>
>>  >>  But client side does not show any responds in the "View Results
>> Tree"
>>  >>  listener.
>>  >>  So, looks like some problem is there.
>>  >>
>>  >>  PS: if i'm using jmeter-server and jmeter-client on same WinXP box -
>>  >>  "remote" testing works fine.
>>  >>
>>  >>
>>  >>  Do you have proper setting in "jmeter" properties file on client
>> side
>>  >> (sh7)?
>>  >>  This setting should be shown in "Run->Remote Start" menu.
>>  >>
>>  >>
>>  >>
>>  >>
>>  >>  Manish Chakravarty-2 wrote:
>>  >>  >
>>  >>  > On Wed, Jun 25, 2008 at 1:30 AM, sebb <[EMAIL PROTECTED]> wrote:
>>  >>  >
>>  >>  >> On 24/06/2008, Manish Chakravarty <[EMAIL PROTECTED]> wrote:
>>  >>  >> > Hello All,
>>  >>  >> >
>>  >>  >> >  I am trying to do remote testing ; with two machines (as a
>>  >> learning
>>  >>  >> > experience )
>>  >>  >> >
>>  >>  >> >  The machines are on the same subnet and are as follows:
>>  >>  >> >  sh6 => jmeter server
>>  >>  >> >  sh7 => jmeter client
>>  >>  >> >
>>  >>  >> >  On sh6 I start the jmeter server from the command line
>>  >>  >> >  On sh7 i start the jmeter client as follows:
>>  >>  >> >
>>  >>  >> >  [EMAIL PROTECTED]:~# jakarta-jmeter-2.3.1/bin/jmeter -n -r -t
>> TestFile.jmx
>>  >> -l
>>  >>  >> > logremote.jtl
>>  >>  >> >  (I have already configured sh7's jmeter.properties and pointed
>> it
>>  >> to
>>  >>  >> the
>>  >>  >> IP
>>  >>  >> > address of sh6 )
>>  >>  >> >
>>  >>  >>
>>  >>  >> Current version is 2.3.2
>>  >>  >>
>>  >>  >> >  I see the following output in the console:
>>  >>  >> >  Created the tree successfully
>>  >>  >> >  Configuring remote engine for 67.207.142.28
>>  >>  >> >  Starting remote engines
>>  >>  >> >  Starting the test @ Tue Jun 24 19:24:53 UTC 2008
>> (1214335493204)
>>  >>  >> >  Remote engines have been started
>>  >>  >> >
>>  >>  >> >
>>  >>  >> >  on sh6 (the server) , I see the following output:
>>  >>  >> >
>>  >>  >> >  [EMAIL PROTECTED]:~# tail jmeter-server.log
>>  >>  >> >  2008/06/24 19:14:30 INFO  - jmeter.JMeter: JMeter 
>> Locale=English
>>  >>  >> (United
>>  >>  >> > States)
>>  >>  >> >  2008/06/24 19:14:30 INFO  - jmeter.JMeter:
>>  >>  >> > JMeterHome=/root/jakarta-jmeter-2.3.1
>>  >>  >> >  2008/06/24 19:14:30 INFO  - jmeter.JMeter: user.dir  =/root
>>  >>  >> >  2008/06/24 19:14:30 INFO  - jmeter.JMeter: PWD       =/root
>>  >>  >> >  2008/06/24 19:14:30 INFO  -
>>  >>  >> > jmeter.engine.RemoteJMeterEngineImpl: Starting backing
>>  >>  >> > engine on 1099
>>  >>  >> >  2008/06/24 19:14:30 INFO  -
>>  >>  >> > jmeter.engine.RemoteJMeterEngineImpl: Creating RMI registry
>>  >>  >> > (server.rmi.create=true)
>>  >>  >> >  2008/06/24 19:14:30 INFO  -
>>  >>  >> > jmeter.engine.RemoteJMeterEngineImpl: Creating JMeter
>>  >>  >> > engine on host sh6
>>  >>  >> >  2008/06/24 19:14:30 INFO  -
>>  >>  >> > jmeter.engine.StandardJMeterEngine: Listeners will be
>>  >>  >> > started after enabling running version
>>  >>  >> >  2008/06/24 19:14:30 INFO  -
>>  >>  >> > jmeter.engine.StandardJMeterEngine: To revert to the
>>  >>  >> > earlier behaviour, define
>>  >>  >> > jmeterengine.startlistenerslater=false
>>  >>  >> >  2008/06/24 19:14:30 INFO  -
>>  >>  >> > jmeter.engine.RemoteJMeterEngineImpl: Bound to registry on
>>  >>  >> > port 1099
>>  >>  >> >
>>  >>  >> >
>>  >>  >> >  After this /nothing/ seems to happen. I see Java utilizing any
>>  >> CPU.
>>  >>  >> >  To ensure that something is running on sh6 I do the following:
>>  >>  >> >  [EMAIL PROTECTED]:~# ps -ef | grep java
>>  >>  >> >  root     27653 27651  0 18:45 pts/0    00:00:00 java -server
>>  >> -Xms256m
>>  >>  >> > -Xmx256m -XX:NewSize=128m -XX:MaxNewSize=128m
>>  >>  >> -XX:MaxTenuringThreshold=2
>>  >>  >> > -Dsun.rmi.dgc.client.gcInterval=600000
>>  >>  >> > -Dsun.rmi.dgc.server.gcInterval=600000 -XX:PermSize=64m
>>  >>  >> > -XX:MaxPermSize=64m -jar
>>  >>  >> > jakarta-jmeter-2.3.1/bin/ApacheJMeter.jar
>>  >>  >> > -Dserver_port=1099 -s -j jmeter-server.log
>>  >>  >> >
>>  >>  >> >  This clearly shows that the server is listening on port 1099.
>>  >>  >> >
>>  >>  >> >  A telnet to port 1099 on sh6 confirms that it is indeed open.
>>  >>  >> >
>>  >>  >> >  I wait for a long time and nothing happens.
>>  >>  >> >  Am I doing something wrong? Why is the test not running?
>>  >>  >> >
>>  >>  >> >  Any help on this topic would be very useful!
>>  >>  >>
>>  >>  >> What does the client jmeter log show?
>>  >>  >
>>  >>  >
>>  >>  >
>>  >>  > The client JMeter log shows this:
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.util.JMeterUtils: Setting
>> Locale to
>>  >>  > en_US
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.JMeter: Loading user properties
>>  >> from:
>>  >>  > /root/jakarta-jmeter-2.3.1/bin/user.properties
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.JMeter: Loading system
>> properties
>>  >> from:
>>  >>  > /root/jakarta-jmeter-2.3.1/bin/system.properties
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.JMeter: Copyright (c) 1998-2007
>> The
>>  >>  > Apache Software Foundation
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.JMeter: Version 2.3.1
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.JMeter: java.version=1.6.0_06
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.JMeter: os.name=Linux
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.JMeter: os.arch=amd64
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.JMeter: os.version=2.6.18-xen
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.JMeter:
>>  >> file.encoding=ANSI_X3.4-1968
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.JMeter: Default Locale=English
>>  >> (United
>>  >>  > States)
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.JMeter: JMeter  Locale=English
>>  >> (United
>>  >>  > States)
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.JMeter:
>>  >>  > JMeterHome=/root/jakarta-jmeter-2.3.1
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.JMeter: user.dir  =/root
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.JMeter: PWD       =/root
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.services.FileServer: Default
>>  >> base=/root
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.services.FileServer: Set new
>>  >> base=/root
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.JMeter: Loading file:
>>  >>  > joyent-testing-onlyHtml.jmx
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.save.SaveService: Testplan
>> (JMX)
>>  >>  > version:
>>  >>  > 2.2. Testlog (JTL) version: 2.2
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.save.SaveService: Using
>> SaveService
>>  >>  > properties file encoding UTF-8
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.save.SaveService: Using
>> SaveService
>>  >>  > properties file version 594567
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.samplers.SampleResult: Note:
>> Sample
>>  >>  > TimeStamps are START times
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.samplers.SampleResult:
>>  >>  > sampleresult.default.encoding is set to ISO-8859-1
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.save.SaveService: Using
>> SaveService
>>  >>  > properties version 2.0
>>  >>  > 2008/06/24 19:24:52 INFO  - jmeter.save.SaveService: All converter
>>  >>  > versions
>>  >>  > present and correct
>>  >>  > 2008/06/24 19:24:52 INFO  -
>>  >> jmeter.protocol.http.sampler.HTTPSamplerBase:
>>  >>  > Cannot find .className property for htmlParser, using default
>>  >>  > 2008/06/24 19:24:52 INFO  -
>>  >> jmeter.protocol.http.sampler.HTTPSamplerBase:
>>  >>  > Parser for text/html is
>>  >>  > 2008/06/24 19:24:52 INFO  -
>>  >> jmeter.protocol.http.sampler.HTTPSamplerBase:
>>  >>  > Parser for application/xhtml+xml is
>>  >>  > 2008/06/24 19:24:52 INFO  -
>>  >> jmeter.protocol.http.sampler.HTTPSamplerBase:
>>  >>  > Parser for application/xml is
>>  >>  > 2008/06/24 19:24:52 INFO  -
>>  >> jmeter.protocol.http.sampler.HTTPSamplerBase:
>>  >>  > Parser for text/xml is
>>  >>  > 2008/06/24 19:24:52 INFO  -
>>  >> jmeter.protocol.http.sampler.HTTPSamplerBase:
>>  >>  > Parser for text/vnd.wap.wml is
>>  >>  > org.apache.jmeter.protocol.http.parser.RegexpHTMLParser
>>  >>  > 2008/06/24 19:24:52 INFO  -
>> jmeter.protocol.http.sampler.HTTPSampler:
>>  >>  > Maximum connection retries = 10
>>  >>  > 2008/06/24 19:24:53 INFO  - jmeter.engine.ClientJMeterEngine:
>> Sending
>>  >>  > properties {}
>>  >>  > 2008/06/24 19:24:53 WARN  - jmeter.engine.ClientJMeterEngine:
>> Could
>>  >> not
>>  >>  > set
>>  >>  > properties: java.rmi.ConnectException: Connection refused to host:
>>  >>  > 127.0.0.1;
>>  >>  > nested exception is:
>>  >>  > java.net.ConnectException: Connection refused
>>  >>  >
>>  >>
>>  >> > Do you have proper setting in "jmeter" properties file on client
>> side
>>  >>  > (sh7)?
>>  >>  > This setting should be shown in "Run->Remote Start" menu.
>>  >>
>>  >> >
>>  >>  > 2008/06/24 19:24:53 INFO  - jmeter.engine.ClientJMeterEngine:
>> about to
>>  >> run
>>  >>  > remote test
>>  >>  > 2008/06/24 19:24:53 INFO  - jmeter.engine.ClientJMeterEngine: done
>>  >>  > initiating run command
>>  >>  > 2008/06/24 19:24:53 INFO  - jmeter.engine.ClientJMeterEngine:
>> running
>>  >>  > clientengine run method
>>  >>  > 2008/06/24 19:24:53 INFO  - jmeter.engine.ConvertListeners: num
>>  >> threads =
>>  >>  > 10
>>  >>  > 2008/06/24 19:24:53 INFO  - jmeter.samplers.StandardSampleSender:
>>  >> Using
>>  >>  > Standard Remote Sampler for this test run
>>  >>  > 2008/06/24 19:24:53 INFO  - jmeter.samplers.StandardSampleSender:
>>  >> Using
>>  >>  > Standard Remote Sampler for this test run
>>  >>  > 2008/06/24 19:24:53 INFO  - jmeter.samplers.StandardSampleSender:
>>  >> Using
>>  >>  > Standard Remote Sampler for this test run
>>  >>  > 2008/06/24 19:24:53 INFO  - jmeter.samplers.StandardSampleSender:
>>  >> Using
>>  >>  > Standard Remote Sampler for this test run
>>  >>  > 2008/06/24 19:24:53 ERROR - jmeter.engine.ClientJMeterEngine:
>>  >>  >  java.rmi.ConnectException: Connection refused to host: 127.0.0.1;
>>  >> nested
>>  >>  > exception is:
>>  >>  > java.net.ConnectException: Connection refused
>>  >>  > at
>> sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
>>  >>  > at
>>  >>
>> sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
>>  >>  > at
>> sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
>>  >>  > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:110)
>>  >>  > 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:619)
>>  >>  > Caused by: java.net.ConnectException: Connection refused
>>  >>  > at java.net.PlainSocketImpl.socketConnect(Native Method)
>>  >>  > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>>  >>  > at
>> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>>  >>  > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>>  >>  > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>>  >>  > at java.net.Socket.connect(Socket.java:519)
>>  >>  > at java.net.Socket.connect(Socket.java:469)
>>  >>  > at java.net.Socket.<init>(Socket.java:366)
>>  >>  > at java.net.Socket.<init>(Socket.java:180)
>>  >>  > 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:595)
>>  >>  > ... 6 more
>>  >>  >
>>  >>  >
>>  >>  > I am baffled because I have set the jmeter.properties to point to
>> the
>>  >>  > other
>>  >>  > host. Why is it picking up 127.0.0.1 ?
>>  >>  >
>>  >>  >
>>  >>
>>  >>
>>  >> --
>>  >>  View this message in context:
>>  >>
>> http://www.nabble.com/JMeter-remote-distributed-testing-not-working--No-error-message-in-log-tp18098637p18389965.html
>>  >>  Sent from the JMeter - User mailing list archive at Nabble.com.
>>  >>
>>  >>
>>  >>
>>  >> 
>> ---------------------------------------------------------------------
>>  >>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>>  >>  For additional commands, e-mail: [EMAIL PROTECTED]
>>  >>
>>  >>
>>  >
>>  > ---------------------------------------------------------------------
>>  > To unsubscribe, e-mail: [EMAIL PROTECTED]
>>  > For additional commands, e-mail: [EMAIL PROTECTED]
>>  >
>>  >
>>  >
>>
>>
>> --
>>  View this message in context:
>> http://www.nabble.com/JMeter-remote-distributed-testing-not-working--No-error-message-in-log-tp18098637p18392320.html
>>
>> Sent from the JMeter - User mailing list archive at Nabble.com.
>>
>>
>>  ---------------------------------------------------------------------
>>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>>  For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/JMeter-remote-distributed-testing-not-working--No-error-message-in-log-tp18098637p18392611.html
Sent from the JMeter - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


      

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to