On 03/06/2009, uzfarid <[email protected]> wrote:
>
>  Hi,
>
>  Strange thing is that with second host (the one which has problem) user ramp
>  up works fine until some number, sometimes 300, sometimes less or more. then
>  it starts giving that error message above.

What happens if you run that host on its own? Does it still fail?

>  Br,
>
>  Farid
>
>
>  sebb-2-2 wrote:
>  >
>  > If JMeter works OK with one server host but not the other, then the
>  > likelihood is that there is a problem with the host or the connection
>  > to it.
>  >
>  > On 03/06/2009, uzfarid <[email protected]> wrote:
>  >>
>  >>  changing JVM versions did not fix this problem unfortunately...
>  >>
>  >>
>  >>
>  >>
>  >>  uzfarid wrote:
>  >>  >
>  >>  > I checked hardware statistics.
>  >>  >
>  >>  > Load was not generated from second slave machine even though users
>  >> were
>  >>  > ramped up.
>  >>  >
>  >>  > I checked JVM versions and saw that they are different. Now i am
>  >> making
>  >>  > them use one version and see if it solves this problem.
>  >>  >
>  >>  >
>  >>  > uzfarid wrote:
>  >>  >>
>  >>  >> Hi,
>  >>  >>
>  >>  >> I did Jmeter remote testing with 3 machines, 1 being master and other
>  >> 2
>  >>  >> slaves.
>  >>  >>
>  >>  >> In one of slave machines ramping up users went ok but in between I
>  >> keep
>  >>  >> getting the following error:
>  >>  >>
>  >>  >> ERROR - jmeter.samplers.StandardSampleSender: sampleOccurred
>  >>  >> 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.samplers.RemoteSampleListenerImpl_Stub.sampleOccurred(Unknown
>  >>  >> Source)
>  >>  >>      at
>  >>  >>
>  >> 
> org.apache.jmeter.samplers.StandardSampleSender.sampleOccurred(StandardSampleSender.java:68)
>  >>  >>      at
>  >>  >>
>  >> 
> org.apache.jmeter.samplers.RemoteListenerWrapper.sampleOccurred(RemoteListenerWrapper.java:86)
>  >>  >>      at
>  >>  >>
>  >> 
> org.apache.jmeter.threads.ListenerNotifier.notifyListeners(ListenerNotifier.java:86)
>  >>  >>      at
>  >>  >>
>  >> 
> org.apache.jmeter.threads.JMeterThread.notifyListeners(JMeterThread.java:673)
>  >>  >>      at
>  >>  >>
>  >> 
> org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:360)
>  >>  >>      at
>  >> org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:243)
>  >>  >>      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)
>  >>  >>      ... 9 more
>  >>  >>
>  >>  >> Does this mean that in reality this slave machine did not run the
>  >>  >> script?? or what is reason for this error?
>  >>  >>
>  >>  >> Thank you.
>  >>  >>
>  >>  >> Br,
>  >>  >>
>  >>  >> Farid
>  >>  >>
>  >>  >
>  >>  >
>  >>
>  >>  --
>  >>
>  >> View this message in context:
>  >> 
> http://www.nabble.com/Jmeter-2.3.3-Remote-testing-problem-tp23847444p23852472.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-2.3.3-Remote-testing-problem-tp23847444p23855518.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