jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrey Pokhilko <>
Subject Re: Hanging test due to no timeout set / hanging sampler and Test duration
Date Fri, 24 Nov 2017 13:44:25 GMT

First of all, I agree that this is very confusing for users. We need to
not fall into this trap by default.

Wouldn't changing default timeout for HTTP sampler help in this case?
Just default how we set it for newly added samplers. This way it won't
affect existing test plans, but will make users by default to have
limited socket waiting time. Something like 30-60 seconds is a good
default from my practice.

Andrey Pokhilko

24.11.2017 15:15, Philippe Mouawad пишет:
> Hello,
> Currently when you check Schedule in Thread group and:
>    - fix a duration for your test
>    - Don't set any timeout on HTTP requests or use a non interruptible
>    sampler
> Your test can hang infinitely as JMeter will not interrupt the Hanging
> samplers even after duration of Thread Group has been reached.
> This is a frequent problem faced by JMeter users (I remember that I have
> answered this SO question at least 10 times). Even non newbie can get
> trapped.
> Shouldn't we introduce this to avoid hanging test that give a feeling of
> broken JMeter while the problem is in the hanging targetted server ?:
>    - Option 1: Add an option in Scheduler part called "Interrupt pending
>    Threads after duration + security margin (1m) that could be a field or
>    property" on Thread Group (checked by default)
>    - Option 2 : Add it at test plan level to avoid repeating the
>    configuration
>    - On start of Thread Group, an additional TimerTask would be triggered
>    after duration + security margin and would do the following:
>       - run equivalent (refactor) of code at:
>          -
> Cordialement.
> Philippe Mouawad.
> Ubik-Ingénierie
> UBIK LOAD PACK Web Site <>

View raw message