On 10/10/06, Benjamin Novack <[EMAIL PROTECTED]> wrote:
Hi,
I'm currently using JMeter to benchmark some web services (eg, SOAP
requests) that go through a broker for various numbers of simultaneous
users. Due to what appears to be a bug in the broker, a handful (2-8) of
the first requests to go through the broker get 'stuck,' and never
return. My previous testing tool, SOATest, handled the situation
relatively gracefully, and simply declared those users to have
experienced a time-out error when they hit the time-out value. I've
tried adding a Duration Assertion into my test plan as a child of the
SOAP Request.. It appears to function correctly - ie, if I set it for
3000 milliseconds, a 'normal' request that takes longer will be marked
appropriately, and the test will move on. But for these 'lost' requests,
the test _never_ acknowledges that they should be timed out - in fact,
at the end of the time allotted for the test, the threads keep running
indefinitely, and I have to manually kill the test. The log asserts that
those threads "Won't die." The behavior I expected - and desired - was
that the threads should simply hit the value in the Duration Assertion
element and immediately be killed off, marked as errors. Any thoughts as
to what's going on?
The purpose of Assertions is to decide if a completed sample passes
certain criteria or not.
They don't affect the Sampler itself - if the sampler does not
complete, then the Assertions will not be run.
As to why the sampler never completes: JMeter does not currently set
any timeouts on the HTTPSampler or SOAP Samplers.
Depending on which sampler you are using (I can't tell from the log),
you may be able to set a system property to enable a timeout.
==
JMeter could probably be enhanced to support timeouts for certain
samplers - if you want this, please create a Bugzilla enhancement
request.
[Depending on the underlying protocol stack, this may have to be a
global timeout rather than per sampler.]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
