Hi George,
> if (!headerOK) {
> method.releaseConnection();
> throw new
> InvalidMIMETypeException(offendingHeader);
> }
You don't have to release the connection here, since that will be
done in the finally{} block. You could call method.abort() to make
*really* sure the connection is not re-used. But I doubt that will
make a difference, since you already set the Connection: close
header before.
The connection manager is configured for 2000 connections, is this
also the number of threads you are using simultaneously?
If performance is an issue for your application, you should call
httpClient.execute(HostConfiguration, HttpMethod, HttpState)
with a dedicated state for each thread or a new state for each
request, depending on your usage scenario. Otherwise, all of your
threads will collect the cookies they receive in the same default
state. Access to the default state is synchronized, and searching
for matching cookies in the whole collection could eventually
serialize all of your requests. That's on top of the delay for
searching through all the cookies by string-matching host names.
hope that helps,
Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
