https://bz.apache.org/bugzilla/show_bug.cgi?id=63004
Philippe Mouawad <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO OS| |All CC| |[email protected] | |om --- Comment #1 from Philippe Mouawad <[email protected]> --- (In reply to RuThaNiel van den Naar from comment #0) > Hello, > im using Jmeter for 12 years now, but there are everything new strange bugs. > > I met strange problem with new HTTP application, which im testing, in > browser are response times from 2-20s for whole pages for all requests, this > 1 problematic is 0-8s, in Jmeter for 1 request was response time almost > always 30s+, in very few occasional iterations im getting fast response time > 1-8s, but when i get slow its always over (like some wait is added or > something like that) 30s, 30-38s. I run zillion of iterations, but i never > got response between 8s and 29s!, always 30+, or <8s. > > I kept, investigating and when i used Java client+RedirectAutomatically > option instead of HTTPclient4 is fine,i getting reasonable response times > 0-8s. Any other any other combinations, failing, i tried httpclient4 with > redirectAutomatically too, its the same, its still slow, +30s.. in 95% of > cases. Its not some application hicup or something its reproducable, whole > day long problem. > > I tried Jmeter 4/3.3 even Jmeter 3 with HTTP client3 and its accross > multiple of version, there is some bug. > > Its simple scripts, no timers, no cycles etc.. just requests, transaction > controller and lots of regular expression extractors and few results tree. > Load is 1 to 5 users. Java 1.8 64 bit 1.8 191. > > Im using OpenVPN for scripting, antivir is turn down, but condion for all > testing are the same. > > Application+data are not public, but i know that im doing, same scenario > in SilkPerformer is fast too. Hello, 1/ Can you attach a sample test plan ? Or at least show your configuration: - of HTTP Request - Thread Group - HTTP Cookie Manager - HTTP Header Manager 2/ Also please provide jmeter.log after activating debug mode: in bin/log4j2.xml uncomment lines 75 / 76: <Logger name="org.apache.http" level="debug" /> <Logger name="org.apache.jmeter.protocol.http" level="debug" /> Start jmeter and run the "buggy" request once . 3/ If you can also put fiddler capture. 4/ Also please provide some context on application With current status Thank you -- You are receiving this mail because: You are the assignee for the bug.
