Hello Tony, Tony Thompson wrote: > MultiThreadedHttpConnectionManager opens a new connection for every > request until the pool gets back up to 50 again. When submitting only > one request per second, I would have expected only one connection to be > opened and reused. If I submit only one request per second before the > pool suddenly grew and then shrunk, it only opens one connection. When > the IdleConnectionTimeoutThread clears idle connections, shouldn't the > connection manager start shrinking the pool back down as it becomes more > idle instead of instantly trying to grow it back up to 50 even though > load doesn't warrant it?
This issue is known and will be fixed in version 3.1: https://issues.apache.org/jira/browse/HTTPCLIENT-597 cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
