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 own response timeout of 10s.
- the webservice ws2 has 2 methods, m1
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
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
application servers. If fact, it's common the user changes these
On Fri, 2018-10-19 at 16:02 +0200, Joan Balagueró wrote:
> Hello,
>
>
>
> Just three more questions:
>
>
>
> 1. Is this the way to set a byte array to the RequestBuilder’s
> entity
> (using a org.apache.http.nio.entity.NByteArrayEntity)?
>
>
>
>
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).
>
>
>
Hello,
Just three more questions:
1. Is this the way to set a byte array to the RequestBuilders entity
(using a org.apache.http.nio.entity.NByteArrayEntity)?
org.apache.hc.client5.http.classic.methods.RequestBuilder.RequestBuilder rb
= RequestBuilder.post(uri);
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)).
