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 set the SO_TIMEOUT HttpClient.setTimeout(), connection timeout HttpClient.setHttpConnectionFactoryTimeout(), and the connection manager's timeout HttpClient.setHttpConnectionFactoryTimeout(). If one of the threads is getting locked up somewhere this should ferret it out.

Mike

On Mar 4, 2004, at 10:34 PM, Tony Thompson wrote:

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 before (we
have this application running in lots of different situations and it
runs perfectly) so, I don't even know of a situation I can't simulate
the problem with.

Any other ideas?  I am not really that familiar with the HTTP client
code but, I could try digging around if you have any ideas about what I
might look at.

Tony

[EMAIL PROTECTED] 03/04/04 09:57PM >>>
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 get a wire log but, it doesn't look very helpful. I
am
attaching it anyway.

Tony

[EMAIL PROTECTED] 03/03/04 08:22PM >>>
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 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 something I need to configure differently to get around this
situation?

I am using JDK 1.4.2 but, I have tried different JVMs and it
doesn't
make any difference. The response that the client is receiving is
in
response to a POST and it is coming back in several continuation
packets
(don't know if that matters).

Thanks.
Tony



---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]

<WireTrace.txt>


---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to