Hello,
Ok by me for 60 or 115s
This should be marked as incompatible changes in release notes.
Regards
On Thu, Dec 26, 2019 at 12:14 PM Felix Schumacher <
felix.schumac...@internetallee.de> wrote:
>
> Am 25.12.19 um 12:42 schrieb Vladimir Sitnikov:
> >> more connections on the
> > client, which
Am 25.12.19 um 12:42 schrieb Vladimir Sitnikov:
>> more connections on the
> client, which can be a sparse resource.
>
> It does not typically exceed the number of threads, so users would expect
> that.
>
> The problem with the current default is it makes the false sense of
> enabling keep-alive
>more connections on the
client, which can be a sparse resource.
It does not typically exceed the number of threads, so users would expect
that.
The problem with the current default is it makes the false sense of
enabling keep-alive in UI.
The users might think that they activate KA, but it is
Hi,
JMeter defaults to 2 seconds timeout for keep-alive HTTP connections, which
seems to be much less than the typical browser configuration.
https://en.wikipedia.org/wiki/HTTP_persistent_connection#Use_in_web_browsers
,
https://fastmail.blog/2011/06/28/http-keep-alive-connection-timeouts/
