olegk wrote: > > TSCM is perfectly capable of reducing the size of its pool after a spike > of activity. It will be gradually removing connections from the pool as > they become expired. One can have a better control of this process by > running a helper thread and calling #closeExpiredConnections() or > #closeIdleConnections() every once in a while. > > That's why I personally see no harm in keeping the maximum number of > connections per host set to a fairly high value, as long as you do not > mind having lots and lots of connections as a result of a sudden burst > of requests. >
Oh cool I didn't realize TSCCM did that. Thanks. -- View this message in context: http://www.nabble.com/ThreadSafeClientConnManager-and-pool-size-tp21079444p21146125.html Sent from the HttpClient-User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
