If you are using a separate instance of HttpClient within each thread and only executing one request/response at a time per thread, there is no need for the MultiThreadedHttpConnectionManager. My guess is there is either a problem with the target or perhaps how you are executing the requests. Please take a look at the troubleshooting guide <http://jakarta.apache.org/commons/httpclient/troubleshooting.html> for some more ideas.
Mike
On Mar 8, 2004, at 8:20 AM, Brookes, Mark, GBPM wrote:
Hi,
I am developing an internal test product which performs a set of parallel connections to a test target. The way I have designed and implemented this is that a number of threads are created to simulate loading - each thread creates an HttpClient, executes the required methods on it and checks that the responses received are valid before terminating the thread. I am not using the MultiThreadedHttpConnectionManager as I do not belive it is needed as each connection is entirely managed within its own thread and is, therefore, not actually multi-threaded.
However, after just a few threads are started (currently about 3) I begin to get null pages being received - is this due to me not using the MultiThreadedHttpConnectionManageer or is it actually a problem with the test target?
Mark Brookes
Location Based Service Assistant Chief Engineer
Vodafone Global Products & Services Ltd - (WHQ - Edison House)
Tel: +44(0)1635 673835
Mobile: +44(0)7766 478305
Email: [EMAIL PROTECTED]
Vodafone Global Products & Services Ltd
Registered Office: Vodafone House, The Connection, Newbury, Berkshire, RG14 2FN, UK
Registered in England No. 3802001
--------------------------------------------------------------------- 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]
