Hi Mark,
By default HttpClient makes use of the SimpleHttpConnectionManager.
This connection manager only supports one request at a time. Each
request, including the response, must be fully complete before the next
begins. Sounds like the MultiThreadedHttpConnectionManager might be
more
Hi Joe,
Read timeouts will cause exceptions to be thrown from within
HttpMethod.execute().
Mike
McMahon, Joseph wrote:
I have a client program that uses the MultiThreadedHttpConnectionManager and
after a while, it seems like the connections hang. I haven't traced
anything yet to know the
Ok, do you know what exception? I'd rather not do a generic Exception catch
for this issue.
Thanks
-Original Message-
From: Michael Becke [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 03, 2004 12:43 PM
To: Commons HttpClient Project
Subject: Re: Timeout exception
Hi Joe,
Read
Hi Joe,
Unfortunately I don't have the code in front of me at the moment. I
think it will be an HttpRecoverableException (for HttpClient 2.0). If
you set a very low timeout (~1ms) you should be able to test this quite
easily.
Mike
McMahon, Joseph wrote:
Ok, do you know what exception?
I am having an issue with the HTTP client hanging when it is trying to
receive a large amount of data from a web server. After doing a packet
trace, I noticed that as the HTTP client is receiving a large amount of
data, the TCP window size goes to zero and communication just stops. Is
there
Yep, thats the solution. Thanks a bunch.
Michael Becke wrote:
Hi Mark,
By default HttpClient makes use of the SimpleHttpConnectionManager. This
connection manager only supports one request at a time. Each request,
including the response, must be fully complete before the next begins.
I know there have been several discussions in regards to streaming requests
rather than buffering. There have been many suggestions on how to allow
for streaming of requests using Piped streams, etc, but I have come up
against a situation were it seems to be impossible to do with the current
Hi David,
In the case of the piped streams you need to do the reading and writing
from separate threads. This is to avoid the exact case that you are
seeing, and I believe it is documented in Sun's javadocs. Any other
solution will require changing the PostMethod API as discussed, or
Hi Tony,
Can you give an example of the code you are using, and where exactly
things are hanging? Also, a wire log may also be helpful
http://jakarta.apache.org/commons/httpclient/logging.html.
Mike
On Mar 3, 2004, at 2:32 PM, Tony Thompson wrote:
I am having an issue with the HTTP client
Mike,
It may be tough to get a wire log because I am seeing this at a
customer site and they may be sensitive about their data. I will check
into it though.
Here is roughly what I do:
1. I create a POST method and set the following
method.setPath();
method.setQueryString();
Oh, there seems to be a lack of documentation on this. Actually a
TimeoutController.TimeoutException extends java.lang.Exception
from the o.a.c.h.util package will be thrown. Timeouts are managed by
the TimeoutController class.
HTH
Ortwin Glück
McMahon, Joseph wrote:
Ok, do you know what
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27426.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hello Ramakrishna,
if you are developing the server system, then HttpClient is
not the way to go. If you are developing a client application,
then it is.
Yes, users should authenticate.
cheers,
Roland
Ramakrishna Kuppa (Bangalore) [EMAIL PROTECTED]
03.03.2004 08:59
Please respond to
Ortwin Glück wrote:
Oh, there seems to be a lack of documentation on this. Actually a
TimeoutController.TimeoutException extends java.lang.Exception
from the o.a.c.h.util package will be thrown. Timeouts are managed by
the TimeoutController class.
HTH
Ortwin Glück
I have to correct myself.
14 matches
Mail list logo
