>If the thread takes too long (more than 5 seconds) to stop, then
>JMeter logs the fact.
In this case, I saw responses as high as 75 seconds - so that is
certainly likely.
>> The warn 2008/12/22 05:01:01 WARN - jmeter.sampler.TestAction:
Could
>> not create number from
>That should only be reported if the Test Action is set to PAUSE.
>> The only test action I have is a beanshell expression which has
>>
>>
${__BeanShell(org.apache.jmeter.threads.JMeterContextService.getNumberOf
>> Threads()<=(1+${__P(p_pbthreadcount,1)}))}
>I don't see how you can use that directly in a Test Action element.
>The Test Action element requires a number (if pause is selected), not
>"true" or "false".
>What are the Test Action target and action?
The test action was stop test. So there might be an issue there.
>The Result Collector uses the testEnded() method call to count down
>the number of outstanding threads, and closes the file(s) when none
>remain.
>It looks like these methods are not called if the test ends abnormally.
That was the thing though.. the test didn't end abnormally, at least
what jmeter reported as error code and in the log. However, I do recall
not seeing the lines I normally see at the end of the test. Example,
here is what I normally see as jmeter is ran from my nant scripts
[exec] Starting the test @ Mon Dec 22 15:29:26 CET 2008
(1229956166059)
[exec] Tidying up ... @ Mon Dec 22 15:35:14 CET 2008
(1229956514977)
[exec] ... end of run
In this fail case, I would never see the tidying up or end of run lines.
Once I cleared up the server side issue, the test performed normally
again. So some combination of a sampler that is taking too long to
complete, plus the test action stop test is pretty much what happened
here I suppose.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
