The error in log looks like the following. It is shown before first request, which is sent, and many times after, but any other request is not sent. In apache access_log, only the first request of each thread shows up.

2008/04/22 18:12:10 ERROR - jmeter.samplers.RemoteTestListenerWrapper: java.rmi.ConnectException: Connection refused to host: 127.0.1.1 <http://127.0.1.1>; ne
sted exception is:
       java.net.ConnectException: Connection refused: connect^M
       at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)^M
at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)^M
       at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)^M
       at sun.rmi.server.UnicastRef.invoke(Unknown Source)^M
at org.apache.jmeter.samplers.RemoteSampleListenerImpl_Stub.testStarted(Unknown Source)^M at org.apache.jmeter.samplers.RemoteTestListenerWrapper.testStarted(RemoteTestListenerWrapper.java:65)^M at org.apache.jmeter.engine.StandardJMeterEngine.notifyTestListenersOfStart(StandardJMeterEngine.java:233)^M at org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:364)^M
       at java.lang.Thread.run(Unknown Source)^M
Caused by: java.net.ConnectException: Connection refused: connect^M
       at java.net.PlainSocketImpl.socketConnect(Native Method)^M
       at java.net.PlainSocketImpl.doConnect(Unknown Source)^M
       at java.net.PlainSocketImpl.connectToAddress(Unknown Source)^M
       at java.net.PlainSocketImpl.connect(Unknown Source)^M
       at java.net.SocksSocketImpl.connect(Unknown Source)^M
       at java.net.Socket.connect(Unknown Source)^M
       at java.net.Socket.connect(Unknown Source)^M
       at java.net.Socket.<init>(Unknown Source)^M
       at java.net.Socket.<init>(Unknown Source)^M
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown Source)^M at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown Source)^M
       ... 9 more^M

sebb a écrit :
On 22/04/2008, Romain Dorgueil <[EMAIL PROTECTED]> wrote:
ok, just found the reason: JMeter server batch launch script does not like
being launched under cygwin environment.


The jmeter-server script works fine for me on Cygwin - what problem did you see?

What does the jmeter-server.log file show?

 sorry for the noise :)

 Romain Dorgueil a écrit :


Hello

I'm new to this list, and to JMeter, so maybe (for sure?) I did something
wrong, but I tryed tuning and hacking as much as I could and I still have
the same problem.
Here it is

I wrote a test scenario, that works just as I wanted if ran locally (with
or without the gui). Basically, it runs one request every seconds in each
threads from this sampler list: fetch an homepage, try to login and fail,
try to log and success, browse some pages, logout, reload homepage.
As said, if I run this scenario with the local client, it works just fine.
But for my needs, I need to have 8 machines running this simultaneous, so I
installed JMeter on a test machine, and ran jmeter-server.bat which launches
successfully. Then, I added its IP to jmeter.properties, and asked my GUI to
make the server run the test scenario. Server displays "Starting the test on
host x.y.z.w @ ......"
I then switch to my web server and tail -f the access log to see if
everything is fine, but each threads only run the first sampler of my
scenario... whatever I do, all following requests are not sent...
I really can't figure out what I did wrong, I hope someone help cause I'm
a bit lost^^
Thanks

 Romain Dorgueil
 Symfony developer
 http://www.symfony-project.com/
 http://www.sensiolabs.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]





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

Reply via email to