Hi Oleg,
> 1. Why, exactly in the same load conditions, a pool with 600 connections is
> more than enough for the blocking client and not enough for the async one?
>
I cannot answer this question unless I can analyze and re-run the benchmark
used to load test both clients.
--> ok, I'll retest
On Thu, 2016-10-27 at 15:13 +0200, Joan Balagueró wrote:
> Hi Oleg,
>
> Sorry yes, reviewing emails I already asked about TimeoutException. I've been
> reading again the httpcore tutorial because think I had a misunderstanding
> about how the async client works.
>
> In the previous case we had
a higher value as Stefan said
previously?
Thanks in advance,
Joan.
-Mensaje original-
De: Oleg Kalnichevski [mailto:ol...@apache.org]
Enviado el: jueves, 27 de octubre de 2016 13:48
Para: HttpClient User Discussion
Asunto: Re: java.util.concurrent.TimeoutException with the async
On Thu, 2016-10-27 at 12:23 +0200, Joan Balagueró wrote:
> Hello,
>
> After working in production with the async client (instead of the blocking
> one) everything seems ok, except that now I can see this error
> intermitently:
>
> java.util.concurrent.TimeoutException
> at
>
with the async client
Hello,
After working in production with the async client (instead of the blocking
one) everything seems ok, except that now I can see this error
intermitently:
java.util.concurrent.TimeoutException
at
org.apache.http.nio.pool.AbstractNIOConnPool.processPendingRequest
Hello,
After working in production with the async client (instead of the blocking
one) everything seems ok, except that now I can see this error
intermitently:
java.util.concurrent.TimeoutException
at
org.apache.http.nio.pool.AbstractNIOConnPool.processPendingRequest(AbstractN
