On Sun, 2014-02-16 at 14:15 +0100, Philippe Mouawad wrote:
> Hello Oleg,
> We have one enabled using:
> new DefaultHttpRequestRetryHandler(RETRY_COUNT, false)
>
> RETRY_COUNT is set to 0 by default but can be changed.
>
> Do you mean we should not set it to 0 ?
This obviously needs to be a posit
Hello Oleg,
We have one enabled using:
new DefaultHttpRequestRetryHandler(RETRY_COUNT, false)
RETRY_COUNT is set to 0 by default but can be changed.
Do you mean we should not set it to 0 ?
Regards
Philippe
On Sat, Feb 15, 2014 at 4:39 PM, Oleg Kalnichevski wrote:
> On Sat, 2014-02-15 at 16:01
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 spe
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 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 shoul
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 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 Kal
Hello ,
yes that's it.
regards
On Saturday, February 15, 2014, Oleg Kalnichevski
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:
> > https://issues.apa
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:
> https://t
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:
https://twitter.com/cfwhisperer/status/428278488349417472
Regards
Philippe
On We
On Tue, 2013-12-10 at 21:38 +0100, Philippe Mouawad wrote:
> Hello Oleg,
> Thanks for answer.
> Wouldn't it be interesting to add some threshold or delay between each
> check instead of doing check on each request ?
>
> Regards
> Philippe
>
Philippe
I am not sure it is worth the trouble. In mos
Hello Oleg,
Thanks for answer.
Wouldn't it be interesting to add some threshold or delay between each
check instead of doing check on each request ?
Regards
Philippe
On Mon, Dec 9, 2013 at 11:59 AM, Oleg Kalnichevski wrote:
> On Sun, 2013-12-08 at 21:32 +0100, Philippe Mouawad wrote:
> > Hello
On Sun, 2013-12-08 at 21:32 +0100, Philippe Mouawad wrote:
> Hello,
> Profiling JMeter, I noticed an important number of SocketTimeoutException
> being triggered without any impact on response status.
>
> I investigated it a bit deeper and find out it affected only HttpClient
> implementations.
>
13 matches
Mail list logo
