Thanks Oleg, is there anything I can do in the pool configuration to mitigate
this effect?
-Mensaje original-
De: Oleg Kalnichevski [mailto:ol...@apache.org]
Enviado el: lunes, 3 de octubre de 2016 21:32
Para: HttpClient User Discussion
Asunto: Re: TimeoutException in async pool
On Mon
nnections.
>
>
This is because of the lock contention.
Oleg
> -Mensaje original-
> De: Stefan Magnus Landrø [mailto:stefan.lan...@gmail.com]
> Enviado el: lunes, 3 de octubre de 2016 9:00
> Para: HttpClient User Discussion
> Asunto: Re: TimeoutException in async pool
>
>
...@gmail.com]
Enviado el: lunes, 3 de octubre de 2016 9:00
Para: HttpClient User Discussion
Asunto: Re: TimeoutException in async pool
So - first I'd set pool size to 50 since that's all you need on average. Then
set acquisition timeout to something that makes sense. 10-20ms?
Sendt fra min iPhone
So - first I'd set pool size to 50 since that's all you need on average. Then
set acquisition timeout to something that makes sense. 10-20ms?
Sendt fra min iPhone
> Den 3. okt. 2016 kl. 07.32 skrev Joan Balagueró
> :
>
> Hello,
>
> I’m using the async
Hello,
Im using the async PoolingNHttpClientConnectionManager (v 4.1.2).
Occasionally Im getting this error:
java.util.concurrent.TimeoutException
at
org.apache.http.nio.pool.AbstractNIOConnPool.processPendingRequest(AbstractN
IOConnPool.java:364)
at