On Sat, Dec 19, 2020 at 5:40 PM Graham Russell <[email protected]> wrote:
> I think it's a good idea, as long as we make it very obvious how to change > it in the UI and failure/error message. > Yes > > Would it affect existing scripts? I can imagine some existing (and indeed > new) tests might start failing with a 60s read timeout due to some slow > calls. > Yes that's the impact but if we clearly document this, do you think it is a problem ? > > Graham > > > On Sat, 19 Dec 2020, 16:10 Philippe Mouawad, < > [email protected]> > wrote: > > > Hello > > > > Currently we don't set neither connect nor read timeout which means they > > default to infinite. > > I don't think those are good defaults and users frequently think JMeter > is > > hanging. > > > > Shouldn't we set better defaults ? > > > > - Connect to 10s > > - Read to 60s > > > > WDYT ? > > Thanks > > -- > > Regards > > Philippe M. > > > -- Cordialement. Philippe Mouawad.
