On Fri, 2014-02-14 at 15:42 +0100, Philippe Mouawad wrote:
Hello Oleg,
We set this configuration in JMeter 2.11, we got recently this bug report
related to this change:
https://issues.apache.org/bugzilla/show_bug.cgi?id=56119
This issue seems to be faced by another person:
Hello ,
yes that's it.
regards
On Saturday, February 15, 2014, Oleg Kalnichevski o...@ok2consulting.com
wrote:
On Fri, 2014-02-14 at 15:42 +0100, Philippe Mouawad wrote:
Hello Oleg,
We set this configuration in JMeter 2.11, we got recently this bug report
related to this change:
On Sat, 2014-02-15 at 11:22 +0100, Sebastiano Vigna wrote:
Something happened from HttpClient 4.3.1 to 4.3.2.
All of a sudden, we are seeing an immense amount of CPU spent into inflating
compressed HTTP responses. We were experimenting 5000 pages/s two months
ago, but less than 1200
On Sat, 2014-02-15 at 11:23 +0100, Philippe Mouawad wrote:
Hello ,
yes that's it.
regards
Then, I am not sure I understand the problem. The stale connection check
is about trading off some performance for fewer i/o errors or visa
versa.
Oleg
On Saturday, February 15, 2014, Oleg
Hello Oleg,
The problem is that is seems in this particular case, removing this check
it leads to 50% error.
I could be explained by a max number of requests per connection setting, as
per their documentation:
- http://aws.amazon.com/articles/1904
Also, don't overuse a connection. Amazon S3 will
On Sat, 2014-02-15 at 14:46 +0100, Philippe Mouawad wrote:
Hello Oleg,
The problem is that is seems in this particular case, removing this check
it leads to 50% error.
What kind of HttpRequestRetryHandler implementation does JMeter 2.11
use? Usually with the stale check disabled one should
By default we disable retry but it can be controlled by a parameter.
Thanks for the info on ConnectionReuseStrategy, it will be a way to handle
these kind of issues.
Regards
On Sat, Feb 15, 2014 at 3:12 PM, Oleg Kalnichevski
ol...@apache.orgjavascript:_e(%7B%7D,'cvml','ol...@apache.org');
Also remember that JMeter has a Use keepalive option on the HTTP Sampler GUI.
If unchecked, JMeter will send Connection: close (or equivalent) as
part of the request.
[This does not work reliably for Java HTTP because the connections may
be pooled]
On 15 February 2014 15:01, Philippe Mouawad
On Sat, 2014-02-15 at 16:01 +0100, Philippe Mouawad wrote:
By default we disable retry but it can be controlled by a parameter.
I have say you may want to have a retry handler enabled by default if
the stale check is off. At the very least you may want to retry
idempotent requests or some
On 15 Feb 2014, at 12:47 PM, Oleg Kalnichevski ol...@apache.org wrote:
The problem mostly likely has been introduced by HTTPCLIENT-1432 [1]. I
reviewed the patch once more and could not find anything obviously wrong
with it. Try reverting the changes introduced by HTTPCLIENT-1432 and see
On Sat, 2014-02-15 at 17:06 +0100, Sebastiano Vigna wrote:
On 15 Feb 2014, at 12:47 PM, Oleg Kalnichevski ol...@apache.org wrote:
The problem mostly likely has been introduced by HTTPCLIENT-1432 [1]. I
reviewed the patch once more and could not find anything obviously wrong
with it. Try
11 matches
Mail list logo
