jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Sitnikov <>
Subject Re: HTTP Request: Modify Timeout Default Values
Date Mon, 07 May 2018 20:15:44 GMT
>They are currently infinite and frequently I see users on Stackoverflow

Could you provide examples?

> or in real life think that JMeter has hanged

Does that mean "I've started the load and nothing happens"?
Could we draw a spinner that does somehow clarify if JMeter is fine?
Currently we have "number of active threads", however it does not
distinguish between a thread hitting the server and a thread blocked on a

I'm not sure if adding a UI for user-facing thread dump is a good thing,
but I'm always ending up with capturing thread dumps.

>   - 3 sec for connect timeout
>   - 30 sec for read timeout

The listed values might be too low for those who test 10+ second response

There's a note that Chrome/Firefox were happy to wait for 1500 seconds:


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message