I need to implement a scenario where a http request is sent to the same host by multiple threads and requires login but the login credentials are always same. In order to avoid logging in all the time I am planning to use a single instance of HTTPClient with a multithreaded connection manager. However, while testing I ran into scenarios where different threads were waiting infinitely for a connection. This seems to happen when the number of threads is close to the maximum number of connections set up for the connection manager. In general what is the connection pooling strategy for this connection manager? Does the pool grow in size as the number of simultaneous requests are greater than the configured pool size? Is there an alternate way to achieve what I am trying to do? regards Monmohan -- View this message in context: http://old.nabble.com/httpclient-and-mulitthreaded-connection-manager-tp26312457p26312457.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]
