Nothing special. A series of HTTP Samplers paced using a Constant Throughput
Controller:
Thread Group
HTTP Sampler
Constant Throughput Controller
HTTP Sampler
HTTP Sampler
Gaussian Random Timer
I tried using a timeout - no difference. It's worth noting that in every case
if I close the dialogue and retry the stop test command it works straight away.
It's only ever the last 1 or 2 threads that get hung.
On 15 Jan 2014, at 11:42, Flavio Cysne <[email protected]> wrote:
> It have happened to me when network devices get overcharged and start
> dropping packages.
> I overcome this issue defining a timeout; in my case, using HTTP Request
> samplers, connection and response timeouts.
>
> What samplers are you using?
>
>
> 2014/1/15 Oliver Lloyd <[email protected]>
>
>> I wanted to check this here first before raising an issue. I see this
>> message pretty much every single time I try stopping a test. It's been a
>> part of JMeter for me for quite a while now and even appears to be an issue
>> when running headless, I now include steps in my automation scripts that
>> will kill the jmeter pid when the stop call fails.
>>
>> Is it just me?
>> ---------------------------------------------------------------------
>> 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]
