Thanks .. I am using setMaxConnectionsPerHost()... and not setMaxTotalConnections(). Assuming there is a fixed number of hosts, will there be a fixed number of sockets used ?
Also were there any API or behavioral changes (besides bug fixes :-)) between 2.0 rc1 and final that I should be aware of? Or is there a doc somewhere that has the list of changes between rc1 and final?
Thanks again!
-Eric
Michael Becke wrote:
On Mar 17, 2004, at 5:05 PM, Eric Bloch wrote:
Thanks... just to be clear though... the multi-threadded connection mgr should never hold open more than a fixed number of sockets though, right?
Yes, any one instance of MultiThreadedHttpConnectionManager will only have a certain number of open connections. This is configurable via setMaxTotalConnections(). You will need to ensure that you are reusing the same instance of the connection manager.
There were also a number of bugs fixed in the MultiThreadedHttpConnectionManager between 2.0 RC1 and the final 2.0 relase. I would suggest upgrading to 2.0 just to be sure.
Mike
---------------------------------------------------------------------
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]
