I'm trying to get remote invocation of jmeter working in order to
perform a load test of my company's website, and it is almost, but not
quite actually happening.
The client (zorak) is a Windows XP SP 1 desktop with the Sun JDK 5.0 and the
Windows Firewall disabled:
java version "1.5.0_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08)
Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode, sharing)
The server (moltar) is a RedHat 8.0 server with kernel 2.4.18-14smp,
all iptables rules set to "ACCEPT" and the Sun JDK 1.4:
java version "1.4.2_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_07-b05)
Java HotSpot(TM) Client VM (build 1.4.2_07-b05, mixed mode)
Per the recent thread, I removed the "127.0.0.1" line from
c:\windows\drivers\etc\hosts on the client, and altered the
jmeter-server startup script to (a) run rmiregistry with debugging
turned up, and (b) start jmeter-server with
'-Djava.rmi.server.hostname=moltar'. "Moltar" in /etc/hosts points to
the ip address of the ethernet, not loopback interface. Moltar and
the zorak are both on the same subnet (10.1.1.0/24).
The rmiregistry starts up, and the jmeter-server appears to connect to
it, but when the client attempts to connect to the server, I see the
following in the jmeter.log file:
2005/03/04 16:52:35 INFO - jmeter.JMeter: Version 2.0.2
2005/03/04 16:52:35 INFO - jmeter.JMeter: java.version=1.5.0_01
2005/03/04 16:52:35 INFO - jmeter.JMeter: Copyright (c) 1998-2004 The Apache
Software Foundation
2005/03/04 16:52:45 INFO - jmeter.gui.action.Load: Loading file: C:\Documents
and
Settings\nmehl\Desktop\jakarta-jmeter-2.0.2\bin\testfiles\Fundfire_Legacy_Test.jmx
2005/03/04 16:53:06 INFO - jmeter.engine.ClientJMeterEngine: about to run
remote test
2005/03/04 16:53:06 INFO - jmeter.engine.ClientJMeterEngine: done initiating
run command
2005/03/04 16:53:06 INFO - jmeter.engine.ClientJMeterEngine: running
clientengine run method
2005/03/04 16:53:06 INFO - jmeter.engine.ConvertListeners: num threads = 6
2005/03/04 16:53:06 INFO - jmeter.engine.ConvertListeners: num threads = 6
2005/03/04 16:53:06 INFO - jmeter.engine.ClientJMeterEngine: sent host
=10.1.1.248
2005/03/04 16:53:06 ERROR - jmeter.engine.ClientJMeterEngine:
java.rmi.MarshalException: error marshalling arguments; nested
exception is:
java.net.SocketException: Connection reset by peer: socket write error
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at
org.apache.jmeter.engine.RemoteJMeterEngineImpl_Stub.configure(Unknown Source)
at
org.apache.jmeter.engine.ClientJMeterEngine.run(ClientJMeterEngine.java:126)
at java.lang.Thread.run(Unknown Source) Caused by:
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
at java.io.BufferedOutputStream.write(Unknown Source) at
java.io.ObjectOutputStream$BlockDataOutputStream.drain(Unknown Source)
at java.io.ObjectOutputStream$BlockDataOutputStream.writeByte(Unknown
Source)
at java.io.ObjectOutputStream.writeFatalException(Unknown Source)
at java.io.ObjectOutputStream.writeObject(Unknown Source)
at sun.rmi.server.UnicastRef.marshalValue(Unknown Source)
... 4 more
On the server side, I see the following from rmiregistry (clocks are
not synced, so ignore the timestamps):
Mar 5, 2005 6:02:11 AM sun.rmi.transport.tcp.TCPTransport$ConnectionHandler run
FINE: RMI TCP Connection(2)-10.1.1.71: accepted socket from [10.1.1.71:3423]
Mar 5, 2005 6:02:11 AM sun.rmi.transport.tcp.TCPTransport$ConnectionHandler run
FINER: RMI TCP Connection(2)-10.1.1.71: (port 1099) suggesting 10.1.1.71:3423
Mar 5, 2005 6:02:11 AM sun.rmi.transport.tcp.TCPTransport$ConnectionHandler run
FINER: RMI TCP Connection(2)-10.1.1.71: (port 1099) client using 10.1.1.71:0
Mar 5, 2005 6:02:11 AM sun.rmi.transport.tcp.TCPTransport handleMessages
FINE: RMI TCP Connection(2)-10.1.1.71: (port 1099) op = 80
Mar 5, 2005 6:02:11 AM sun.rmi.transport.StreamRemoteCall getInputStream
FINER: RMI TCP Connection(2)-10.1.1.71: getting input stream
Mar 5, 2005 6:02:11 AM sun.rmi.transport.Transport serviceCall
FINER: RMI TCP Connection(2)-10.1.1.71: call dispatcher
Mar 5, 2005 6:02:11 AM sun.rmi.transport.StreamRemoteCall getOutputStream
FINER: RMI TCP Connection(2)-10.1.1.71: getting output stream
Mar 5, 2005 6:02:11 AM sun.rmi.transport.tcp.TCPChannel$Reaper run
FINER: RMI ConnectionExpiration-[moltar:53098]: wake up
Mar 5, 2005 6:02:11 AM sun.rmi.transport.tcp.TCPChannel freeCachedConnections
FINER: RMI ConnectionExpiration-[moltar:53098]: connection timeout expired
Mar 5, 2005 6:02:11 AM sun.rmi.transport.tcp.TCPConnection close
FINE: RMI ConnectionExpiration-[moltar:53098]: close connection
Mar 5, 2005 6:02:11 AM sun.rmi.transport.tcp.TCPChannel$Reaper run
FINER: RMI ConnectionExpiration-[moltar:53098]: exit
Mar 5, 2005 6:02:11 AM sun.rmi.transport.tcp.TCPTransport handleMessages
FINE: RMI TCP Connection(1)-10.1.1.248: (port 1099) connection closed
Mar 5, 2005 6:02:11 AM sun.rmi.transport.tcp.TCPConnection close
FINE: RMI TCP Connection(1)-10.1.1.248: close connection
Mar 5, 2005 6:02:11 AM sun.rmi.transport.tcp.TCPTransport handleMessages
FINE: RMI TCP Connection(2)-10.1.1.71: (port 1099) op = 82
Mar 5, 2005 6:02:11 AM sun.rmi.transport.tcp.TCPTransport handleMessages
FINE: RMI TCP Connection(2)-10.1.1.71: (port 1099) op = 84
...and that is about all she wrote. Any help that the list could
offer here would be well appreciated.
-n
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
