, 10 de noviembre de 2018 19:30
Para: HttpClient User Discussion
Asunto: Re: RV: Migration from Async 4.1.3 to HttpClient 5
On Sat, 2018-11-10 at 18:02 +0100, Joan Balagueró - ventusproxy wrote:
> Hello Oleg,
>
> Sorry, but I think I'm going to need a bit more help to finish
>
Even having pooled connections to reuse, shouldn't
> the max_conn value have preference?
>
> 2. Is TEST 5 ok? It seems the 'DefaultMaxPerRoute' cannot be applied
> on the fly in a lax pool. It should have a value of 5000 but it's
> preserving the previous value of 1 (test 4).
&g
g the previous
value of 1 (test 4).
Thanks ,
Joan.
-Mensaje original-
De: Oleg Kalnichevski [mailto:ol...@apache.org]
Enviado el: viernes, 9 de noviembre de 2018 15:31
Para: HttpClient User Discussion
Asunto: Re: RV: Migration from Async 4.1.3 to HttpClient 5
On Fri, 2018-11-09 at
the lax pool, only max per route.
>
Hi,
Can you make sure this is Javadoc'd in the right places if it is not
already?
Gary
>
> Oleg
>
>
> > Thanks,
> >
> > Joan.
> >
> >
> > -Mensaje original-----
> > De: Oleg Kalnichevski [mailto:ol...@apa
t; >
>
> Max total is not enforced by the lax pool, only max per route.
>
> Oleg
>
>
> > Thanks,
> >
> > Joan.
> >
> >
> > -Mensaje original-
> > De: Oleg Kalnichevski [mailto:ol...@apache.org] Enviado el: jueves,
> > 8
>
Joan.
-Mensaje original-
De: Oleg Kalnichevski [mailto:ol...@apache.org]
Enviado el: viernes, 9 de noviembre de 2018 15:01
Para: HttpClient User Discussion
Asunto: Re: RV: Migration from Async 4.1.3 to HttpClient 5
On Fri, 2018-11-09 at 13:39 +0100, Joan Balagueró wrote:
> Thanks Oleg.
l: jueves, 8 de noviembre de 2018 11:04
> Para: HttpClient User Discussion
> Asunto: Re: RV: Migration from Async 4.1.3 to HttpClient 5
>
> On Wed, 2018-11-07 at 19:30 +0100, Joan Balagueró wrote:
> > Hello Oleg,
> >
> > We are finishing the migration and have the
[mailto:ol...@apache.org]
Enviado el: jueves, 8 de noviembre de 2018 11:04
Para: HttpClient User Discussion
Asunto: Re: RV: Migration from Async 4.1.3 to HttpClient 5
On Wed, 2018-11-07 at 19:30 +0100, Joan Balagueró wrote:
> Hello Oleg,
>
> We are finishing the migration and have the last
On Wed, 2018-11-07 at 19:30 +0100, Joan Balagueró wrote:
> Hello Oleg,
>
> We are finishing the migration and have the last questions:
>
> 1. If a connection is kept-alive for 30s at second 0, and after 10s
> is reused, this connection will die at second 30 or will survive
> until second 40?
Kee
Hello Oleg,
We are finishing the migration and have the last questions:
1. If a connection is kept-alive for 30s at second 0, and after 10s is reused,
this connection will die at second 30 or will survive until second 40?
2. Regarding the RetryHandler, below the method inherited from http 4.5 a
Hi Oleg,
Thanks! I'll try it asap
Joan.
-Mensaje original-
De: Oleg Kalnichevski [mailto:ol...@apache.org]
Enviado el: martes, 23 de octubre de 2018 9:28
Para: HttpClient User Discussion
Asunto: Re: Migration from Async 4.1.3 to HttpClient 5
On Mon, 2018-10-22 at 20:40 +0200,
commit/75ca519314b783ba0d314e84f3a7e3488a7c968c
Oleg
>
> -Mensaje original-
> De: Oleg Kalnichevski [mailto:ol...@apache.org]
> Enviado el: domingo, 21 de octubre de 2018 13:11
> Para: HttpClient User Discussion
> Asunto: Re: Migration from Async 4.1.3 to HttpClient 5
>
> On
That would be great.
Thanks Oleg.
-Mensaje original-
De: Oleg Kalnichevski [mailto:ol...@apache.org]
Enviado el: domingo, 21 de octubre de 2018 13:11
Para: HttpClient User Discussion
Asunto: Re: Migration from Async 4.1.3 to HttpClient 5
On Sat, 2018-10-20 at 20:23 +0200, Joan Balagueró
ser Discussion
> Asunto: Re: Migration from Async 4.1.3 to HttpClient 5
>
> On Fri, 2018-10-19 at 21:07 +0200, Joan Balagueró wrote:
> > Hello Oleg,
> >
> > I think it's a bit more complicated ... Let me explain it:
> >
> > - we have a pool with a
ption (and avoid read the
response body content).
Thanks,
Joan.
-Mensaje original-
De: Oleg Kalnichevski [mailto:ol...@apache.org]
Enviado el: sábado, 20 de octubre de 2018 18:17
Para: HttpClient User Discussion
Asunto: Re: Migration from Async 4.1.3 to HttpClient 5
On Fri, 2018-10-1
7;responseReceived' method).
Thanks,
Joan.
-Mensaje original-
De: Oleg Kalnichevski [mailto:ol...@apache.org]
Enviado el: sábado, 20 de octubre de 2018 18:17
Para: HttpClient User Discussion
Asunto: Re: Migration from Async 4.1.3 to HttpClient 5
On Fri, 2018-10-19 at 21:07 +0200, Joa
On Fri, 2018-10-19 at 21:07 +0200, Joan Balagueró wrote:
> Hello Oleg,
>
> I think it's a bit more complicated ... Let me explain it:
>
> - we have a pool with a response timeout of 15s
> - this pool is shared by 2 webservices, ws1 and ws2. Ws1 uses the
> pool's response timeout, but ws2 uses its
is can be solved in any way using
http5?
Thanks,
Joan.
-Mensaje original-
De: Oleg Kalnichevski [mailto:ol...@apache.org]
Enviado el: viernes, 19 de octubre de 2018 18:22
Para: HttpClient User Discussion
Asunto: Re: Migration from Async 4.1.3 to HttpClient 5
On Fri, 2018-10-19 at 18:0
On Fri, 2018-10-19 at 18:01 +0200, Joan Balagueró wrote:
> Hi Oleg,
>
> Thanks a lot for all your answers. I'll work on this a bit more.
>
> There is just one problematic thing for us. Our app is an api
> gateway, and one important piece is the response timeouts between our
> app and the client a
here any way to use a Lax Pool with http1.1 in order to get this
socket timeout at request level?
Thanks,
Joan.
-Mensaje original-
De: Oleg Kalnichevski [mailto:ol...@apache.org]
Enviado el: viernes, 19 de octubre de 2018 17:21
Para: HttpClient User Discussion
Asunto: Re: Migration from
On Fri, 2018-10-19 at 15:08 +0200, Joan Balagueró wrote:
> Hello,
>
>
>
> We are in the process of migrating to HttpClient5 from
> AsyncClient4.1.3, and
> we have some quiestions:
>
>
>
> 1. this.rc =
> RequestConfig.custom().setAuthenticationEnabled(false).
>
>
> setConnectionRequ
Hello,
We are in the process of migrating to HttpClient5 from AsyncClient4.1.3, and
we have some quiestions:
1. this.rc = RequestConfig.custom().setAuthenticationEnabled(false).
setConnectionRequestTimeout(Timeout.ofMillis(this.poolTimeout)).
setConnectionRequestTimeout(this.poo
22 matches
Mail list logo
