Hello David, > I am using a HttpClient object for every user coming to the system. These > are used to store state like cookies etc. Is there a reason why having many > HttpClient objects in memory would keep many sockets open.
by default, each HttpClient object will have it's own connection pool. If you make sure that all your HttpClient objects share a single MultiThreadedHttpConnectionManager, there shouldn't be a problem. Using different HttpClient objects for each user is a waste of resources. Cookies are not stored in the HttpClient object, but in an HttpState object. Keep different HttpState objects for each user and pass them to a single HttpClient object when executing methods, instead of using the default state of different HttpClient objects. hope that helps, Roland
smime.p7s
Description: S/MIME Cryptographic Signature
