es can be really large and I always need to store them in memory for
further processing?
Thanks,
Joan.
-Mensaje original-
De: Oleg Kalnichevski [mailto:ol...@apache.org]
Enviado el: jueves, 17 de marzo de 2016 10:50
Para: HttpClient User Discussion
Asunto: Re: Help with async client
On Thu, 2
to get the IOReactor config from the nio pool.
Thanks,
Joan.
-Mensaje original-
De: Oleg Kalnichevski [mailto:ol...@apache.org]
Enviado el: miércoles, 16 de marzo de 2016 16:22
Para: HttpClient User Discussion
Asunto: Re: Help with async client
On Wed, 2016-03-16 at 15:41 +0100, Joan
s. Any response from the bakcend takes 100ms at least, because a
> Thread.sleep(100) is set before writing any byte to the servletoutputstream.
>
> So, why are these exceptions not triggered?
>
> Thanks,
> Joan.
>
>
>
>
> -Mensaje original-
> D
On Thu, 2016-03-17 at 10:42 +0100, Joan Balagueró wrote:
> Hi Oleg,
>
> Thanks. If I have a 400ms connection timeout and a 850ms response timeout, I
> understand that the select interval must contain the 400ms (the lowest
> value). True?
>
Yes.
> In our app these connection/response timeouts
these exceptions not triggered?
Thanks,
Joan.
-Mensaje original-
De: Oleg Kalnichevski [mailto:ol...@apache.org]
Enviado el: martes, 15 de marzo de 2016 16:14
Para: HttpClient User Discussion
Asunto: Re: Help with async client
On Tue, 2016-03-15 at 15:54 +0100, Joan Balagueró wro
On Thu, 2016-03-17 at 17:51 +0100, Joan Balagueró wrote:
> Hello,
>
> I hope this is the last question ... On our proxy we are reading the response
> from the backend with a FutureCallback. On the complete method,
> we process the response body in this way:
>
> public void
On Tue, 2016-03-15 at 15:54 +0100, Joan Balagueró wrote:
> Hello,
>
>
>
> We have moved from the blocking client (PoolingHttpClientConnectionManager)
> to the async one (PoolingNHttpClientConnectionManager), and we are starting
> some tests to check performance.
>
>
>
> We have a test app
