On Sun, 2018-03-11 at 17:57 +0100, Philippe Mouawad wrote: > It looks a bit aggressive to me, but if you say it’s ok, it’s fine > for me. > > So you confirm I need to keep reference to > poolingHttpClientConnectionManager right ? > No way from httpclient >
HttpClient interface represents a generic client that may not necessarily have a connection pool or even connection manager internally. Coupling HttpClient interface with a specific connection manager would force each and every HttpClient implementation to implement that specific connection management contract as well. Oleg > Thanks > On Sunday, March 11, 2018, Oleg Kalnichevski <ol...@apache.org> > wrote: > > > On Sun, 2018-03-11 at 15:57 +0100, Philippe Mouawad wrote: > > > I mean starting with a fresh sslcontext. > > > It works if I keep a ref on PoolingHttpConnectionManager and call > > > > > > poolingHttppoolingHttpClientConnectionManagerClientConnectionMan > > > > ager.closeExpiredConnections(); > > poolingHttpClientConnectionManager.closeIdleConnections(1L, > > > TimeUnit.MICROSECONDS); > > > > > > > > > But is there a better way ? > > > > What is so bad about using the connection manager to close out all > > persistent connections? > > > > Oleg > > > > ----------------------------------------------------------------- > > ---- > > To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org > > For additional commands, e-mail: httpclient-users-h...@hc.apache.or > > g > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h...@hc.apache.org
