Betr.: Re: Betr.: Re: Connection refused exception

[I....@klaverblad.nl]

Hi Roland,

Thank you for your quick response.

You are right of course, sending one request at a time is perfectly silly
:-) I was only trying it to see if it would make the errors go away. If so,
we would at least know a little more.

I wasn't very clear, sorry. I DO read the response, but I perform an abort
in the finally clause to make sure that the connection will really be
closed. Does that make sense?

Regards,
Iris


---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-user-help@jakarta.apache.org

Re: Betr.: Re: Betr.: Re: Connection refused exception

[Roland Weber <ht...@dubioso.net>]

Hello Iris,

> I wasn't very clear, sorry. I DO read the response, but I perform an abort
> in the finally clause to make sure that the connection will really be
> closed. Does that make sense?

No, not really. Sending the "Connection: close" header and releasing the
connection does a better job of closing the connection. Abort really
makes sense only if you didn't read to the end.

Have you checked the queue size and worker threads of the web server
you are connecting to? Is there a proxy inbetween that might limit
the number of connections? Maybe the web server has some protection
against DoS attacks that is triggered by your application?

cheers,
  Roland

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-user-help@jakarta.apache.org