jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Mouawad <philippe.moua...@gmail.com>
Subject Re: httpclient4.time_to_live defaults to 2000 which is way less than the typical browser behavior
Date Thu, 26 Dec 2019 11:17:39 GMT
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.schumacher@internetallee.de> wrote:

>
> 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 in UI.
> >
> > The users might think that they activate KA, but it is not used if the
> > response times exceed 2sec.
> >
> > Reusing connections after 60seconds might even enable to surface
> > concurrency issues in the app.
>
> What do the others think? I am fine with a change to something higher
> (60s would be OK I guess).
>
> Felix
>
> >
> > Vladimir
> >
>


-- 
Cordialement.
Philippe Mouawad.

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