://jakarta.apache.org/commons/httpclient/threading.html
Hope this helps
Oleg
-Original Message-
From: Foran, Christopher [mailto:[EMAIL PROTECTED]
Sent: Monday, May 03, 2004 16:30
To: [EMAIL PROTECTED]
Subject: Multi-threaded problem (is this a bug?)
I have a java client which is able to
Title: Multi-threaded problem (is this a bug?)
I have a java client which is able to create multiple threads, each thread sends a POST. I am able to run up to 50 threads with out a problem with my current version of the client.
I want to use Httpclient but this version of the java client
;
>
>
>
>
> Michael Becke <[EMAIL PROTECTED]>
> 01.09.2003 21:16
> Please respond to "Commons HttpClient Project"
>
> To: "Commons HttpClient Project"
> <[EMAIL PROTECTED]>
> cc:
> Subject:Re:
stopping to receive, e.g. for SSL connections.
regards,
Roland
Michael Becke <[EMAIL PROTECTED]>
01.09.2003 21:16
Please respond to "Commons HttpClient Project"
To: "Commons HttpClient Project"
<[EMAIL PROTECTED]>
cc:
Subject:
ond to "Commons HttpClient Project"
To: "Commons HttpClient Project"
<[EMAIL PROTECTED]>
cc:
Subject:Re: A bug?
Yes, this is a good point. We might as well be as thorough as possible.
The only real change that might make sense in rever
Yes, this is a good point. We might as well be as thorough as possible.
The only real change that might make sense in reversing the order in
which streams are closed. Is sounds like Yue would like to have the
output stream closed before the input. Anyone have objections to this?
Mike
On Mon
Michael Becke wrote:
> Any thoughts on why we close the streams and then the socket?
Someone might have implemented sockets with buffered streams.
Closing only the socket directly would not dispose of the buffers.
Given the SocketFactory stuff, that possibility shouldn't be ruled out.
just my th
As you note, this is not really a problem as all IOExceptions caused
during close are buried. It would be nice if this worked a little more
cleanly though. I have no idea why we close all of the various streams
and then the socket. It does seems a little redundant. Does closing
the output n
;close->
This exception is throw in perfect normal working condition, so I
suppose it is a bug, although the end user will not notice it. I would
suggest closing output stream before closing input stream in
HttpConnection.closeSocketAndStream().
I am curious, is it really necessary to
()
will be called to convert the exception to a HttpRecoverableException.
This exception is throw in perfect normal working condition, so I
suppose it is a bug, although the end user will not notice it. I would
suggest closing output stream before closing input stream in
10 matches
Mail list logo
