I have checked and:
1. The server and client are on the same PC so this can't be the problem.
2. This could be possible, but an added ~15 seconds for a request with about
150 threads? Seems high to me, especially for a tool which is designed for
load testing..
3. This checkbox is disabled (not selected) everywhere.
4. I'm not sure what you mean with transaction controller? AFAIK I'm not
using one.
This is the part of jmeter.log around the part in which AutoStop stops the
test:
2011/03/29 15:55:27 INFO - jmeter.threads.JMeterThread: Thread started:
Stepping Thread Group 1-150
2011/03/29 15:55:27 INFO - jmeter.threads.JMeterThread: Thread started:
Stepping Thread Group 1-141
2011/03/29 15:55:27 INFO - jmeter.threads.JMeterThread: Thread started:
Stepping Thread Group 1-143
2011/03/29 15:55:27 INFO - kg.apc.jmeter.reporters.AutoStop: Average
Response Time is more than 20000 for 5s. Auto-shutdown test...
2011/03/29 15:55:27 ERROR - jmeter.threads.JMeterThread: Test failed!
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Unknown Source)
at
org.apache.jmeter.engine.StandardJMeterEngine.stopTest(StandardJMeterEngine.
java:342)
at
org.apache.jmeter.engine.StandardJMeterEngine.askThreadsToStop(StandardJMete
rEngine.java:549)
at kg.apc.jmeter.reporters.AutoStop.stopTest(AutoStop.java:279)
at
kg.apc.jmeter.reporters.AutoStop.sampleOccurred(AutoStop.java:65)
at
org.apache.jmeter.threads.ListenerNotifier.notifyListeners(ListenerNotifier.
java:87)
at
org.apache.jmeter.threads.JMeterThread.notifyListeners(JMeterThread.java:694
)
at
org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:362
)
at
org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:243)
at java.lang.Thread.run(Unknown Source)
2011/03/29 15:55:27 INFO - jmeter.threads.JMeterThread: Thread finished:
Stepping Thread Group 1-40
2011/03/29 15:55:27 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Stepping Thread Group 1-40
2011/03/29 15:55:27 INFO - kg.apc.jmeter.reporters.AutoStop: Average
Response Time is more than 20000 for 5s. Auto-shutdown test...
2011/03/29 15:55:27 INFO - jmeter.threads.JMeterThread: Stopping: Stepping
Thread Group 1-657
2011/03/29 15:55:27 INFO - jmeter.threads.JMeterThread: Stopping: Stepping
Thread Group 1-449
CP
-----Original Message-----
From: apc [mailto:[email protected]]
Sent: dinsdag 29 maart 2011 15:38
To: [email protected]
Subject: RE: question about duration assertion
I see several possible reasons:
1. Network latency - some network hardware/software may provide some delays
2. JMeter itself may cause delays at high transaction rates and complex test
plans
3. You use "download embedded resources" checkbox, this causes sampler work
as transaction controller, having sub-samples
4. You use transaction controller itself
--
View this message in context:
http://jmeter.512774.n5.nabble.com/question-about-duration-assertion-tp42690
21p4269409.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]
