Re: Setting better defaults for HTTP request

On Sat, Dec 19, 2020 at 5:40 PM Graham Russell 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

Re: Setting better defaults for HTTP request

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. 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. Graham On Sat, 19 Dec

Setting better defaults for HTTP request

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.

Jenkins build is back to normal : JMeter » JMeter Ubuntu #116

See

Jenkins build is back to normal : JMeter » JMeter-trunk #177

See

[GitHub] [jmeter] pmouawad commented on pull request #637: add: tcp record proxy

pmouawad commented on pull request #637: URL: https://github.com/apache/jmeter/pull/637#issuecomment-748462622 Thank you for taking into account the review. The tests are still failing. One of the issues I see is that you have not updated saveservice.properties (and

[GitHub] [jmeter] pmouawad merged pull request #639: update xstreams to 1.4.15 (from 1.4.14)

pmouawad merged pull request #639: URL: https://github.com/apache/jmeter/pull/639 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

Re: [Bug 64954] Critical Section Controller causes waiting threads not to stop

Hello Felix, Yes Regards On Saturday, December 19, 2020, Felix Schumacher < felix.schumac...@internetallee.de> wrote: > Hi Philippe, > > why did you set version to 2.12? Is this to indicate, that the behaviour > is known since 2.12? > > Regards > > Felix > > Am 19.12.20 um 00:39 schrieb

Re: [Bug 64954] Critical Section Controller causes waiting threads not to stop

Hi Philippe, why did you set version to 2.12? Is this to indicate, that the behaviour is known since 2.12? Regards  Felix Am 19.12.20 um 00:39 schrieb bugzi...@apache.org: > https://bz.apache.org/bugzilla/show_bug.cgi?id=64954 > > Philippe Mouawad changed: > >What|Removed