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 application servers. If fact, it's common the user > changes these response timeouts from the admin console. > > If now they cannot change them on the fly, that means stopping the > http pool, recreating the ioreactor with the new timeout and starting > the pool again, even if this takes just several seconds is something > I cannot do with installations that are processing more than 15.000 > requests per second. > > The main purpose to move to HttpClient5 is the http pool with Lax Max > connections (PoolConcurrencyPolicy.LAX), because we were detecting > contention on the current pool due to the global lock. We don't need > HTTP/2 so, from my ignorance, is there any way to use a Lax Pool > with http1.1 in order to get this socket timeout at request level? >
No, there is not. There will be no request level socket timeout override in HC 5.0 because even with HTTP/1.1 it makes no sense when messages are being pipelined. HC 5.0 could however provide APIs to enumerate all open connection and let their socket timeout get re-set. Feel free to raise a change request for this feature or better yet contribute it. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
