Facing problem with JMeter Distributed Testing
I am trying to to do stress testing through JMeter Distributed testing, i have implemented all steps set-up for remote distibution on console pc as well as remote pc with all configuration but when i am trying to start remote pc thru JMeter on console(GUI JMeter) machine (Run-Remote Start-remote pc IP Address) and run my test plan it does not work. Before run above test plan, i have start JMeter Server on remote machine and after run the test plan its displaying message as below on JMeter server console on remote machine. Found ApacheJMeter_core.jar Starting the test on host 10.82.12.81 @ Thu Oct 09 16:20:18 EDT 2008 (1223583618 687) Finished the test on host 10.82.12.81 @ Thu Oct 09 16:22:13 EDT 2008 (1223583733 153) One more thing i have not found Jmeter.engine.RemoteJMeterEngineImpl: Starting backing engine on JMeter GUI logs file. I think JMeter GUI machine and remote machine has not connected properly but not sure. (Note-After i start remote machine from JMeter GUI, stop Remote machine option is disable) I dont understand where i did the mistake, can anyone suggest me how to go ahead. -- View this message in context: http://www.nabble.com/Facing-problem-with--JMeter-Distributed-Testing-tp19907203p19907203.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]
Re: Jmeter: Distributed Testing Issues
The change of setting the eth0 IP to point to the HOSTNAME (and not the loop back) worked perfectly! Thanks for all your help! On Sat, May 10, 2008 at 6:44 PM, sebb [EMAIL PROTECTED] wrote: On 11/05/2008, Michael McDonnell [EMAIL PROTECTED] wrote: So I should have an entry in my /etc/hosts files that says MyComputer's Host Name MyComputersIP ?? instead of HOSTNAME 127.0.0.1 ? yes (and to play it safe I'll comment out anything that points to 127.0.0.1 ) no, you should probably keep at least: localhost 127.0.0.1 There may be some other loopback entries that are required. Unfortunately, this will have to wait til monday afternoon. Thanks for the super fast response though! Michael On Sat, May 10, 2008 at 6:26 PM, sebb [EMAIL PROTECTED] wrote: On 11/05/2008, Michael McDonnell [EMAIL PROTECTED] wrote: I'm utilizing 4 machines for Jmeter test, one master 3 slaves. The Master Machine is Windows XP SP2 The Slaves are Ubuntu 8.04 (I don't believe this SHOULD matter, but bear with me) The tests are not working on the remote computers only, and I'm not entirely sure why... 1) In order to be assured that port 1099 was open on all the machines, I scanned them all using NMap. 2) To double check they were all on the same subnet, I put them all on a switch with the master. (Their addresses are all 10.237.0.x) 3) To make sure they were all on the same version of jmeter and that the same test and necessary data files were all accessible, I piled my csv and jmx files into the bin folder and ftp'ed them so they were all synchronous. (eventually, I'll just utilize subversion to sync them up, but for now...) 4) To make sure that the jmeter-server bin wasn't failing, I was checking the logs using a tail (tail -f jmeter-server.log in the linux world) No exceptions were found. 5) I was also watching the jmeter log very closely on the master computer. I keep getting the same error: jmeter.samplers.RemoteListenerWrapper: testStarted(host) java.rmi.ConnectException: Connection refused to host: 127.0.1.1; In my jmeter.log file for each remote computer I try to connect to. This usually means that the host database is not set up correctly. Check that the Ubuntu systems know their own IP addresses, and that they are not set to the loopback address. 5a) To double check that I wasn't screwing things up by pointing my jmeter.properties file at the wrong place, I changed the local slave ( 127.0.0.1) to the non-loopback ip (10.237.0.x) and it still worked fine on the local machine. Any help anyone could offer would be fantastically appreciated! Thanks! Michael - 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]
Jmeter: Distributed Testing Issues
I'm utilizing 4 machines for Jmeter test, one master 3 slaves. The Master Machine is Windows XP SP2 The Slaves are Ubuntu 8.04 (I don't believe this SHOULD matter, but bear with me) The tests are not working on the remote computers only, and I'm not entirely sure why... 1) In order to be assured that port 1099 was open on all the machines, I scanned them all using NMap. 2) To double check they were all on the same subnet, I put them all on a switch with the master. (Their addresses are all 10.237.0.x) 3) To make sure they were all on the same version of jmeter and that the same test and necessary data files were all accessible, I piled my csv and jmx files into the bin folder and ftp'ed them so they were all synchronous. (eventually, I'll just utilize subversion to sync them up, but for now...) 4) To make sure that the jmeter-server bin wasn't failing, I was checking the logs using a tail (tail -f jmeter-server.log in the linux world) No exceptions were found. 5) I was also watching the jmeter log very closely on the master computer. I keep getting the same error: jmeter.samplers.RemoteListenerWrapper: testStarted(host) java.rmi.ConnectException: Connection refused to host: 127.0.1.1; In my jmeter.log file for each remote computer I try to connect to. 5a) To double check that I wasn't screwing things up by pointing my jmeter.properties file at the wrong place, I changed the local slave ( 127.0.0.1) to the non-loopback ip (10.237.0.x) and it still worked fine on the local machine. Any help anyone could offer would be fantastically appreciated! Thanks! Michael
Re: Jmeter: Distributed Testing Issues
On 11/05/2008, Michael McDonnell [EMAIL PROTECTED] wrote: I'm utilizing 4 machines for Jmeter test, one master 3 slaves. The Master Machine is Windows XP SP2 The Slaves are Ubuntu 8.04 (I don't believe this SHOULD matter, but bear with me) The tests are not working on the remote computers only, and I'm not entirely sure why... 1) In order to be assured that port 1099 was open on all the machines, I scanned them all using NMap. 2) To double check they were all on the same subnet, I put them all on a switch with the master. (Their addresses are all 10.237.0.x) 3) To make sure they were all on the same version of jmeter and that the same test and necessary data files were all accessible, I piled my csv and jmx files into the bin folder and ftp'ed them so they were all synchronous. (eventually, I'll just utilize subversion to sync them up, but for now...) 4) To make sure that the jmeter-server bin wasn't failing, I was checking the logs using a tail (tail -f jmeter-server.log in the linux world) No exceptions were found. 5) I was also watching the jmeter log very closely on the master computer. I keep getting the same error: jmeter.samplers.RemoteListenerWrapper: testStarted(host) java.rmi.ConnectException: Connection refused to host: 127.0.1.1; In my jmeter.log file for each remote computer I try to connect to. This usually means that the host database is not set up correctly. Check that the Ubuntu systems know their own IP addresses, and that they are not set to the loopback address. 5a) To double check that I wasn't screwing things up by pointing my jmeter.properties file at the wrong place, I changed the local slave ( 127.0.0.1) to the non-loopback ip (10.237.0.x) and it still worked fine on the local machine. Any help anyone could offer would be fantastically appreciated! Thanks! Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jmeter: Distributed Testing Issues
So I should have an entry in my /etc/hosts files that says MyComputer's Host Name MyComputersIP ?? instead of HOSTNAME 127.0.0.1 ? (and to play it safe I'll comment out anything that points to 127.0.0.1) Unfortunately, this will have to wait til monday afternoon. Thanks for the super fast response though! Michael On Sat, May 10, 2008 at 6:26 PM, sebb [EMAIL PROTECTED] wrote: On 11/05/2008, Michael McDonnell [EMAIL PROTECTED] wrote: I'm utilizing 4 machines for Jmeter test, one master 3 slaves. The Master Machine is Windows XP SP2 The Slaves are Ubuntu 8.04 (I don't believe this SHOULD matter, but bear with me) The tests are not working on the remote computers only, and I'm not entirely sure why... 1) In order to be assured that port 1099 was open on all the machines, I scanned them all using NMap. 2) To double check they were all on the same subnet, I put them all on a switch with the master. (Their addresses are all 10.237.0.x) 3) To make sure they were all on the same version of jmeter and that the same test and necessary data files were all accessible, I piled my csv and jmx files into the bin folder and ftp'ed them so they were all synchronous. (eventually, I'll just utilize subversion to sync them up, but for now...) 4) To make sure that the jmeter-server bin wasn't failing, I was checking the logs using a tail (tail -f jmeter-server.log in the linux world) No exceptions were found. 5) I was also watching the jmeter log very closely on the master computer. I keep getting the same error: jmeter.samplers.RemoteListenerWrapper: testStarted(host) java.rmi.ConnectException: Connection refused to host: 127.0.1.1; In my jmeter.log file for each remote computer I try to connect to. This usually means that the host database is not set up correctly. Check that the Ubuntu systems know their own IP addresses, and that they are not set to the loopback address. 5a) To double check that I wasn't screwing things up by pointing my jmeter.properties file at the wrong place, I changed the local slave ( 127.0.0.1) to the non-loopback ip (10.237.0.x) and it still worked fine on the local machine. Any help anyone could offer would be fantastically appreciated! Thanks! Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jmeter: Distributed Testing Issues
On 11/05/2008, Michael McDonnell [EMAIL PROTECTED] wrote: So I should have an entry in my /etc/hosts files that says MyComputer's Host Name MyComputersIP ?? instead of HOSTNAME 127.0.0.1 ? yes (and to play it safe I'll comment out anything that points to 127.0.0.1) no, you should probably keep at least: localhost 127.0.0.1 There may be some other loopback entries that are required. Unfortunately, this will have to wait til monday afternoon. Thanks for the super fast response though! Michael On Sat, May 10, 2008 at 6:26 PM, sebb [EMAIL PROTECTED] wrote: On 11/05/2008, Michael McDonnell [EMAIL PROTECTED] wrote: I'm utilizing 4 machines for Jmeter test, one master 3 slaves. The Master Machine is Windows XP SP2 The Slaves are Ubuntu 8.04 (I don't believe this SHOULD matter, but bear with me) The tests are not working on the remote computers only, and I'm not entirely sure why... 1) In order to be assured that port 1099 was open on all the machines, I scanned them all using NMap. 2) To double check they were all on the same subnet, I put them all on a switch with the master. (Their addresses are all 10.237.0.x) 3) To make sure they were all on the same version of jmeter and that the same test and necessary data files were all accessible, I piled my csv and jmx files into the bin folder and ftp'ed them so they were all synchronous. (eventually, I'll just utilize subversion to sync them up, but for now...) 4) To make sure that the jmeter-server bin wasn't failing, I was checking the logs using a tail (tail -f jmeter-server.log in the linux world) No exceptions were found. 5) I was also watching the jmeter log very closely on the master computer. I keep getting the same error: jmeter.samplers.RemoteListenerWrapper: testStarted(host) java.rmi.ConnectException: Connection refused to host: 127.0.1.1; In my jmeter.log file for each remote computer I try to connect to. This usually means that the host database is not set up correctly. Check that the Ubuntu systems know their own IP addresses, and that they are not set to the loopback address. 5a) To double check that I wasn't screwing things up by pointing my jmeter.properties file at the wrong place, I changed the local slave ( 127.0.0.1) to the non-loopback ip (10.237.0.x) and it still worked fine on the local machine. Any help anyone could offer would be fantastically appreciated! Thanks! Michael - 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]
Re: Problem with JMeter Distributed Testing
That's a bug in the shell script. It was fixed in JMeter 2.3. On 27/10/2007, Bryan Li [EMAIL PROTECTED] wrote: So I was following the JMeter Distributed Testing Step-by-Step tutorial. When I was trying to run the slave system by executing ./jmeter-server I got the following exception: java.lang.IllegalArgumentException: Unknown arg: CLASSPATH= at org.apache.jmeter.JMeter.initializeProperties(JMeter.java:537) at org.apache.jmeter.JMeter.start(JMeter.java:257) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.jmeter.NewDriver.main(NewDriver.java:183) An error occurred: Unknown arg: CLASSPATH= Does anyone have any idea why this happens? Thanks, Bryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Jmeter distributed testing
Hello, I have problems running a Jmeter master (machine where the GUI is present) and Jmeter slave (machine where the test is running) together. It's ok if I don't use JDBC connection configuration in my testplan for database queries. But when I include the JDBC connection configuration, I receive a nullpointer exception: Could not find ApacheJmeter_core.jar ... ... Trying JMETER_HOME=.. Found ApacheJMeter_core.jar [Full GC 6297K-560K(249088K), 0.0373198 secs] Exception in thread Thread-2 java.lang.NullPointerException at org.apache.jmeter.protocol.jdbc.config.DataSourceElement.testStarted( DataSourceElement.java:91) at org.apache.jmeter.protocol.jdbc.config.DataSourceElement.testStarted( DataSourceElement.java:109) at org.apache.jmeter.engine.StandardJMeterEngine.notifyTestListenersOfSt art(StandardJMeterEngine.java:201) at org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngin e.java:315) at java.lang.Thread.run(Unknown Source) Regards, Benny Rogiers
JMeter distributed testing: java.rmi.MarshalException: error marshalling arguments; nested exception is
Hey, I try to use the fonctionnality of Remote Testing. I follow up the tutorial: Distributed testing And i have the feeling to be in a good way, however, it doesn't work, maybe someone can help me to go on in the good way. Situation: - I install Jmeter 2.0.3 on my machine and on the slave machine - The slave system is working , i have in its log: 2006/01/25 14:18:25 INFO - jmeter.engine.RemoteJMeterEngineImpl: Starting backing engine - I load jmeter.bat from my machine - open a simple script - choose remote start - slave machine - in its logs, i have 2006/01/25 15:24:04 INFO - jmeter.engine.RemoteJMeterEngineImpl: Reset 2006/01/25 15:24:04 INFO - jmeter.engine.RemoteJMeterEngineImpl: Reset 2006/01/25 15:24:04 INFO - jmeter.engine.RemoteJMeterEngineImpl: received host: [IP of the slave machine] - in the log of the master: 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: about to run remote test 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: done initiating run command 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: running clientengine run method 2006/01/25 15:24:04 INFO - jmeter.engine.ConvertListeners: num threads = 1 2006/01/25 15:24:04 INFO - jmeter.engine.ConvertListeners: num threads = 1 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: sent host = [IP of the slave machine] 2006/01/25 15:24:04 ERROR - jmeter.engine.ClientJMeterEngine: java.rmi.MarshalException: error marshalling arguments; nested exception is: java.net.SocketException: Software caused connection abort: 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: Software caused connection abort: 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.write(Unknown Source) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(Unknown Source) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Unknow n Source) at java.io.ObjectOutputStream.writeNonProxyDesc(Unknown Source) at java.io.ObjectOutputStream.writeClassDesc(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source) at java.io.ObjectOutputStream.writeObject0(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 Any ideas, about the problem? Thanks in advance, Elisabeth GUERARD
RE: JMeter distributed testing: Space in the path
Sorry, to disturb you again, just to say you that it works now. previously, jmeter was installed to : C:\Program Files\jmeter\jakarta-jmeter-2.0.3\bin now, R:\jmeter\jakarta-jmeter-2.0.3 Elisabeth _ From: GUERARD Elisabeth Sent: 25 January 2006 15:28 To: jmeter-user@jakarta.apache.org Subject: JMeter distributed testing: java.rmi.MarshalException: error marshalling arguments; nested exception is Hey, I try to use the fonctionnality of Remote Testing. I follow up the tutorial: Distributed testing And i have the feeling to be in a good way, however, it doesn't work, maybe someone can help me to go on in the good way. Situation: - I install Jmeter 2.0.3 on my machine and on the slave machine - The slave system is working , i have in its log: 2006/01/25 14:18:25 INFO - jmeter.engine.RemoteJMeterEngineImpl: Starting backing engine - I load jmeter.bat from my machine - open a simple script - choose remote start - slave machine - in its logs, i have 2006/01/25 15:24:04 INFO - jmeter.engine.RemoteJMeterEngineImpl: Reset 2006/01/25 15:24:04 INFO - jmeter.engine.RemoteJMeterEngineImpl: Reset 2006/01/25 15:24:04 INFO - jmeter.engine.RemoteJMeterEngineImpl: received host: [IP of the slave machine] - in the log of the master: 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: about to run remote test 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: done initiating run command 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: running clientengine run method 2006/01/25 15:24:04 INFO - jmeter.engine.ConvertListeners: num threads = 1 2006/01/25 15:24:04 INFO - jmeter.engine.ConvertListeners: num threads = 1 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: sent host = [IP of the slave machine] 2006/01/25 15:24:04 ERROR - jmeter.engine.ClientJMeterEngine: java.rmi.MarshalException: error marshalling arguments; nested exception is: java.net.SocketException: Software caused connection abort: 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: Software caused connection abort: 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.write(Unknown Source) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(Unknown Source) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Unknow n Source) at java.io.ObjectOutputStream.writeNonProxyDesc(Unknown Source) at java.io.ObjectOutputStream.writeClassDesc(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source) at java.io.ObjectOutputStream.writeObject0(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 Any ideas, about the problem? Thanks in advance, Elisabeth GUERARD
Re: JMeter distributed testing: java.rmi.MarshalException: error marshalling arguments; nested exception is
please make sure the location jmeter is installed does not have a space in the path. peter On 1/25/06, GUERARD Elisabeth [EMAIL PROTECTED] wrote: Hey, I try to use the fonctionnality of Remote Testing. I follow up the tutorial: Distributed testing And i have the feeling to be in a good way, however, it doesn't work, maybe someone can help me to go on in the good way. Situation: - I install Jmeter 2.0.3 on my machine and on the slave machine - The slave system is working , i have in its log: 2006/01/25 14:18:25 INFO - jmeter.engine.RemoteJMeterEngineImpl: Starting backing engine - I load jmeter.bat from my machine - open a simple script - choose remote start - slave machine - in its logs, i have 2006/01/25 15:24:04 INFO - jmeter.engine.RemoteJMeterEngineImpl: Reset 2006/01/25 15:24:04 INFO - jmeter.engine.RemoteJMeterEngineImpl: Reset 2006/01/25 15:24:04 INFO - jmeter.engine.RemoteJMeterEngineImpl: received host: [IP of the slave machine] - in the log of the master: 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: about to run remote test 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: done initiating run command 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: running clientengine run method 2006/01/25 15:24:04 INFO - jmeter.engine.ConvertListeners: num threads = 1 2006/01/25 15:24:04 INFO - jmeter.engine.ConvertListeners: num threads = 1 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: sent host = [IP of the slave machine] 2006/01/25 15:24:04 ERROR - jmeter.engine.ClientJMeterEngine: java.rmi.MarshalException: error marshalling arguments; nested exception is: java.net.SocketException: Software caused connection abort: 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: Software caused connection abort: 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.write(Unknown Source) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(Unknown Source) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Unknow n Source) at java.io.ObjectOutputStream.writeNonProxyDesc(Unknown Source) at java.io.ObjectOutputStream.writeClassDesc(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source) at java.io.ObjectOutputStream.writeObject0(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 Any ideas, about the problem? Thanks in advance, Elisabeth GUERARD
Re: JMeter distributed testing: Space in the path
having space in the path generally causes problems in Java. AFAIK, the path issue has been around forever in Java. to work around that, we could convert paths to URL. feel free to file an enhancement bugzilla. peter On 1/25/06, GUERARD Elisabeth [EMAIL PROTECTED] wrote: Sorry, to disturb you again, just to say you that it works now. previously, jmeter was installed to : C:\Program Files\jmeter\jakarta-jmeter-2.0.3\bin now, R:\jmeter\jakarta-jmeter-2.0.3 Elisabeth _ From: GUERARD Elisabeth Sent: 25 January 2006 15:28 To: jmeter-user@jakarta.apache.org Subject: JMeter distributed testing: java.rmi.MarshalException: error marshalling arguments; nested exception is Hey, I try to use the fonctionnality of Remote Testing. I follow up the tutorial: Distributed testing And i have the feeling to be in a good way, however, it doesn't work, maybe someone can help me to go on in the good way. Situation: - I install Jmeter 2.0.3 on my machine and on the slave machine - The slave system is working , i have in its log: 2006/01/25 14:18:25 INFO - jmeter.engine.RemoteJMeterEngineImpl: Starting backing engine - I load jmeter.bat from my machine - open a simple script - choose remote start - slave machine - in its logs, i have 2006/01/25 15:24:04 INFO - jmeter.engine.RemoteJMeterEngineImpl: Reset 2006/01/25 15:24:04 INFO - jmeter.engine.RemoteJMeterEngineImpl: Reset 2006/01/25 15:24:04 INFO - jmeter.engine.RemoteJMeterEngineImpl: received host: [IP of the slave machine] - in the log of the master: 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: about to run remote test 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: done initiating run command 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: running clientengine run method 2006/01/25 15:24:04 INFO - jmeter.engine.ConvertListeners: num threads = 1 2006/01/25 15:24:04 INFO - jmeter.engine.ConvertListeners: num threads = 1 2006/01/25 15:24:04 INFO - jmeter.engine.ClientJMeterEngine: sent host = [IP of the slave machine] 2006/01/25 15:24:04 ERROR - jmeter.engine.ClientJMeterEngine: java.rmi.MarshalException: error marshalling arguments; nested exception is: java.net.SocketException: Software caused connection abort: 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: Software caused connection abort: 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.write(Unknown Source) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(Unknown Source) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Unknow n Source) at java.io.ObjectOutputStream.writeNonProxyDesc(Unknown Source) at java.io.ObjectOutputStream.writeClassDesc(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source) at java.io.ObjectOutputStream.writeObject0(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 Any ideas, about the problem? Thanks in advance, Elisabeth GUERARD
jmeter distributed testing
Mike, Thanks for your help. However, the case is that the Jmeter jars are all identical, meaning all machines have the exact jmeter installation copy on them. What I did was install it on one machine and copy the whole directory to all other machines. Could there be the source of the issue in the installation procedure? Thanks, ChrisBe [EMAIL PROTECTED] wrote: Marshalling exceptions are usually the result of one of the machines having a different jmeter build than the others. You have to make sure that the jmeter jar files on all machines are exactly the same jar (if you rebuild one, you have to copy that jar over to the other machines). It's not good enough to compile the same exact source twice, you have to copy the jars. -Mike On 3 Oct 2003 at 9:49, Christian Bertram wrote: Gidday, I am using jmeter to run tests with 3 boxes to a web app server (run the 3 with the jmeter-server.bat) and using one of them as the client to launch the tests. I have an issue that after the tests are launched, the following error log is generated: 10/03/2003 8:34:10 AM INFO - jmeter.JMeter: Version 1.9.1 10/03/2003 8:35:12 AM WARN - jmeter.engine: received host 10/03/2003 8:35:14 AM WARN - jmeter.engine: received test tree 10/03/2003 8:35:14 AM WARN - jmeter.engine: running test 10/03/2003 8:35:14 AM INFO - jmeter.engine: Running the test! 10/03/2003 8:35:15 AM INFO - jmeter.engine: Starting 1 test threads 10/03/2003 8:35:15 AM INFO - jmeter.engine: Thread User Agent Test1-1 started 10/03/2003 8:35:26 AM INFO - jmeter.engine: Thread User Agent Test1-1 is done 10/03/2003 8:35:26 AM INFO - jmeter.engine: Starting 20 test threads 10/03/2003 8:35:26 AM INFO - jmeter.engine: Thread Burst - 60 hits per minute2-1 started ... 10/03/2003 8:35:37 AM INFO - jmeter.engine: Thread Burst - 60 hits per minute21-20 is done 10/03/2003 8:35:37 AM INFO - jmeter.engine: Starting 20 test threads 10/03/2003 8:35:37 AM INFO - jmeter.engine: Thread Mixed - User Agents, Read/Write, Report Pages22-1 started ... 10/03/2003 8:36:22 AM INFO - jmeter.engine: Thread Mixed - User Agents, Read/Write, Report Pages32-11 is done 10/03/2003 8:36:23 AM INFO - jmeter.engine: Starting 20 test threads 10/03/2003 8:36:23 AM INFO - jmeter.engine: Thread Continual - 60 / hr (~300,000 / 24hrs)42-1 started ... 10/03/2003 8:36:32 AM INFO - jmeter.engine: Thread Continual - 60 / hr (~300,000 / 24hrs)60-19 started 10/03/2003 8:36:32 AM INFO - jmeter.engine: Thread Continual - 60 / hr (~300,000 / 24hrs)61-20 started 10/03/2003 8:45:20 AM ERROR - jmeter.elements: java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: java.net.SocketException: Connection reset at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source) at sun.rmi.server.UnicastRef.invoke(Unknown Source) at org.apache.jmeter.samplers.RemoteSampleListenerImpl_Stub.sam pleOccurred(Unknown Source) at org.apache.jmeter.samplers.RemoteListenerWrapper.sampleOccur red(RemoteListenerWrapper.java:84) at org.apache.jmeter.threads.ListenerNotifier.notifyListeners(Listener Notifier.java:237) at org.apache.jmeter.threads.JMeterThread.notifyListeners(JMeterThr ead.java:398) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:28 3) at java.lang.Thread.run(Unknown Source) Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at java.io.DataInputStream.readByte(Unknown Source) ... 8 more ... The error is repeating 20 times (the number of threads) and then it changes into: ... 10/03/2003 8:45:21 AM ERROR - jmeter.elements: java.rmi.ConnectException: Connection refused to host: 192.168.83.213; nested exception is: java.net.ConnectException: Connection refused: connect 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.samplers.RemoteSampleListenerImpl_Stub.sam pleOccurred(Unknown Source) at org.apache.jmeter.samplers.RemoteListenerWrapper.sampleOccur red(RemoteListenerWrapper.java:84) at org.apache.jmeter.threads.ListenerNotifier.notifyListeners(Listener Notifier.java:237) at org.apache.jmeter.threads.JMeterThread.notifyListeners(JMeterThr ead.java:398) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:28 3) at java.lang.Thread.run(Unknown Source)
Re: jmeter distributed testing
If you copied the jars, that would be sufficient. So, I'm not sure what the problem is. Does the number of users simulated effect the error? Ie, if you run the test with fewer threads, does the error happen as often/quickly? If it's an intermittent thing, that would make it harder to diagnose. Also, make sure there are no firewalls, software or otherwise. -Mike On 7 Oct 2003 at 8:39, Christian Bertram wrote: Mike, Thanks for your help. However, the case is that the Jmeter jars are all identical, meaning all machines have the exact jmeter installation copy on them. What I did was install it on one machine and copy the whole directory to all other machines. Could there be the source of the issue in the installation procedure? Thanks, ChrisBe [EMAIL PROTECTED] wrote: Marshalling exceptions are usually the result of one of the machines having a different jmeter build than the others. You have to make sure that the jmeter jar files on all machines are exactly the same jar (if you rebuild one, you have to copy that jar over to the other machines). It's not good enough to compile the same exact source twice, you have to copy the jars. -Mike On 3 Oct 2003 at 9:49, Christian Bertram wrote: Gidday, I am using jmeter to run tests with 3 boxes to a web app server (run the 3 with the jmeter-server.bat) and using one of them as the client to launch the tests. I have an issue that after the tests are launched, the following error log is generated: 10/03/2003 8:34:10 AM INFO - jmeter.JMeter: Version 1.9.1 10/03/2003 8:35:12 AM WARN - jmeter.engine: received host 10/03/2003 8:35:14 AM WARN - jmeter.engine: received test tree 10/03/2003 8:35:14 AM WARN - jmeter.engine: running test 10/03/2003 8:35:14 AM INFO - jmeter.engine: Running the test! 10/03/2003 8:35:15 AM INFO - jmeter.engine: Starting 1 test threads 10/03/2003 8:35:15 AM INFO - jmeter.engine: Thread User Agent Test1-1 started 10/03/2003 8:35:26 AM INFO - jmeter.engine: Thread User Agent Test1-1 is done 10/03/2003 8:35:26 AM INFO - jmeter.engine: Starting 20 test threads 10/03/2003 8:35:26 AM INFO - jmeter.engine: Thread Burst - 60 hits per minute2-1 started ... 10/03/2003 8:35:37 AM INFO - jmeter.engine: Thread Burst - 60 hits per minute21-20 is done 10/03/2003 8:35:37 AM INFO - jmeter.engine: Starting 20 test threads 10/03/2003 8:35:37 AM INFO - jmeter.engine: Thread Mixed - User Agents, Read/Write, Report Pages22-1 started ... 10/03/2003 8:36:22 AM INFO - jmeter.engine: Thread Mixed - User Agents, Read/Write, Report Pages32-11 is done 10/03/2003 8:36:23 AM INFO - jmeter.engine: Starting 20 test threads 10/03/2003 8:36:23 AM INFO - jmeter.engine: Thread Continual - 60 / hr (~300,000 / 24hrs)42-1 started ... 10/03/2003 8:36:32 AM INFO - jmeter.engine: Thread Continual - 60 / hr (~300,000 / 24hrs)60-19 started 10/03/2003 8:36:32 AM INFO - jmeter.engine: Thread Continual - 60 / hr (~300,000 / 24hrs)61-20 started 10/03/2003 8:45:20 AM ERROR - jmeter.elements: java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: java.net.SocketException: Connection reset at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source) at sun.rmi.server.UnicastRef.invoke(Unknown Source) at org.apache.jmeter.samplers.RemoteSampleListenerImpl_Stub.sa m pleOccurred(Unknown Source) at org.apache.jmeter.samplers.RemoteListenerWrapper.sampleOcc ur red(RemoteListenerWrapper.java:84) at org.apache.jmeter.threads.ListenerNotifier.notifyListeners(Listener Notifier.java:237) at org.apache.jmeter.threads.JMeterThread.notifyListeners(JMeterT hr ead.java:398) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java: 28 3) at java.lang.Thread.run(Unknown Source) Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at java.io.DataInputStream.readByte(Unknown Source) ... 8 more ... The error is repeating 20 times (the number of threads) and then it changes into: ... 10/03/2003 8:45:21 AM ERROR - jmeter.elements: java.rmi.ConnectException: Connection refused to host: 192.168.83.213; nested exception is: java.net.ConnectException: Connection refused: connect at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
jmeter distributed testing
Gidday, I am using jmeter to run tests with 3 boxes to a web app server (run the 3 with the jmeter-server.bat) and using one of them as the client to launch the tests. I have an issue that after the tests are launched, the following error log is generated: 10/03/2003 8:34:10 AM INFO - jmeter.JMeter: Version 1.9.1 10/03/2003 8:35:12 AM WARN - jmeter.engine: received host 10/03/2003 8:35:14 AM WARN - jmeter.engine: received test tree 10/03/2003 8:35:14 AM WARN - jmeter.engine: running test 10/03/2003 8:35:14 AM INFO - jmeter.engine: Running the test! 10/03/2003 8:35:15 AM INFO - jmeter.engine: Starting 1 test threads 10/03/2003 8:35:15 AM INFO - jmeter.engine: Thread User Agent Test1-1 started 10/03/2003 8:35:26 AM INFO - jmeter.engine: Thread User Agent Test1-1 is done 10/03/2003 8:35:26 AM INFO - jmeter.engine: Starting 20 test threads 10/03/2003 8:35:26 AM INFO - jmeter.engine: Thread Burst - 60 hits per minute2-1 started ... 10/03/2003 8:35:37 AM INFO - jmeter.engine: Thread Burst - 60 hits per minute21-20 is done 10/03/2003 8:35:37 AM INFO - jmeter.engine: Starting 20 test threads 10/03/2003 8:35:37 AM INFO - jmeter.engine: Thread Mixed - User Agents, Read/Write, Report Pages22-1 started ... 10/03/2003 8:36:22 AM INFO - jmeter.engine: Thread Mixed - User Agents, Read/Write, Report Pages32-11 is done 10/03/2003 8:36:23 AM INFO - jmeter.engine: Starting 20 test threads 10/03/2003 8:36:23 AM INFO - jmeter.engine: Thread Continual - 60 / hr (~300,000 / 24hrs)42-1 started ... 10/03/2003 8:36:32 AM INFO - jmeter.engine: Thread Continual - 60 / hr (~300,000 / 24hrs)60-19 started 10/03/2003 8:36:32 AM INFO - jmeter.engine: Thread Continual - 60 / hr (~300,000 / 24hrs)61-20 started 10/03/2003 8:45:20 AM ERROR - jmeter.elements: java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: java.net.SocketException: Connection reset at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source) at sun.rmi.server.UnicastRef.invoke(Unknown Source) at org.apache.jmeter.samplers.RemoteSampleListenerImpl_Stub.sampleOccurred(Unknown Source) at org.apache.jmeter.samplers.RemoteListenerWrapper.sampleOccurred(RemoteListenerWrapper.java:84) at org.apache.jmeter.threads.ListenerNotifier.notifyListeners(ListenerNotifier.java:237) at org.apache.jmeter.threads.JMeterThread.notifyListeners(JMeterThread.java:398) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:283) at java.lang.Thread.run(Unknown Source) Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at java.io.DataInputStream.readByte(Unknown Source) ... 8 more ... The error is repeating 20 times (the number of threads) and then it changes into: ... 10/03/2003 8:45:21 AM ERROR - jmeter.elements: java.rmi.ConnectException: Connection refused to host: 192.168.83.213; nested exception is: java.net.ConnectException: Connection refused: connect 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.samplers.RemoteSampleListenerImpl_Stub.sampleOccurred(Unknown Source) at org.apache.jmeter.samplers.RemoteListenerWrapper.sampleOccurred(RemoteListenerWrapper.java:84) at org.apache.jmeter.threads.ListenerNotifier.notifyListeners(ListenerNotifier.java:237) at org.apache.jmeter.threads.JMeterThread.notifyListeners(JMeterThread.java:398) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:283) at java.lang.Thread.run(Unknown Source) Caused by: java.net.ConnectException: Connection refused: 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.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) ... 10 more ... ...where 192.168.83.213 is the machine where the testing client is run. Any help is appreciated. ChrisBe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
