Hi Tony,
Yes, using the MultiThreadedHttpConnectionManager and executing
multiple requests is fine. It just makes it pretty much impossible to
follow in the wire log. If you are unable to create sample that
exhibits the problem I would suggest fiddling with timeouts. In
particular I would
Hi Tony,
There appears to be some strange things happening in your wire log.
Are you executing multiple requests at the same time? Please post the
code (or an approximation) of the code that elicits the problem.
Mike
On Mar 4, 2004, at 10:50 AM, Tony Thompson wrote:
Mike,
I was able to
Mike,
It is possible that multiple request are being executed at the same
time. I am using the MultiThreadedHttpConnectionManager so, I assumed
that was allowed.
I don't think that I can come up with any code that could approximate
this situation either. I have never seen an issue like this
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
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();
