On Mon, 2006-12-04 at 09:52 -0500, Tony Thompson wrote: > Thanks! >
Tony, The HTTPCLIENT-597 fix has been included into HttpClient 3.1-beta1 release. Please consider trying 3.1-beta1 out and letting us know if the problem has been resolved to your satisfaction. Oleg > -----Original Message----- > From: Roland Weber [mailto:[EMAIL PROTECTED] > Sent: Sunday, December 03, 2006 4:41 PM > To: HttpClient User Discussion > Subject: Re: MultiThreadedHttpConnectionManager connection pool in 3.0.1 > > 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] > > This message (and any associated files) is intended only for the > use of the individual or entity to which it is addressed and may > contain information that is confidential, subject to copyright or > constitutes a trade secret. If you are not the intended recipient > you are hereby notified that any dissemination, copying or > distribution of this message, or files associated with this message, > is strictly prohibited. If you have received this message in error, > please notify us immediately by replying to the message and deleting > it from your computer. Messages sent to and from Stoneware, Inc. > may be monitored. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
