On Thu, 2019-06-06 at 18:56 +0200, Joan grupoventus wrote:
> Hi again,
>
> Not sure if we have seen something strange in the current test with
> the keep alive connections. It's just a GET method to get a gif (this
> pool has no keep-alive, that means a 100ms keep-alive). Here the
> complete http
Hi again,
Not sure if we have seen something strange in the current test with the keep
alive connections. It's just a GET method to get a gif (this pool has no
keep-alive, that means a 100ms keep-alive). Here the complete http log:
https://github.com/joanbalaguero/HttpClient.git (it's the
Hi Oleg,
One more information I forgot to provide, not sure if it can help.
>From the 08.13:00 to 08:13:59 the pool kept exhausted:
08:13:00.211Connection request: [route: {}->http://10.15.15.41:8081][total
kept alive: 0; route allocated: 6 of 1500; total allocated: 1500 of 1500]
( . . . .)
On Thu, 2019-06-06 at 14:34 +0200, Joan grupoventus wrote:
> No .. that's the point ... we are trying any kind of tests ... no
> success. Did you see the 'ServerHttpResponse.java' code? Do you think
> the code is correct?
>
I cannot say 10% without seeing the complete code base.
Oleg
> We are
No .. that's the point ... we are trying any kind of tests ... no success. Did
you see the 'ServerHttpResponse.java' code? Do you think the code is correct?
We are thinking to replace the HttpClient5 by the AsyncClient1.3 and leave the
rest of our code untouched and check again. So at least we
On Wed, 2019-06-05 at 16:19 +0200, Joan grupoventus wrote:
> Hi Oleg,
>
> Still dealing with this stuck connections. I could get traces from
> httpClient5 and we see all connections busy:
> 08:12:56.031 ex-00E1DFB8: acquiring connection with route {}->
> http://10.15.15.14:8082
> 08:12:56.087
