DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28354>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28354

unable to find line starting with "HTTP" message when timeout occurs





------- Additional Comments From [EMAIL PROTECTED]  2004-04-13 04:16 -------
Hi Oleg,

You are right - "the problem is in fact caused by the server dropping 
connection" (maybe not the server but the HTTP commons-client, what is ok and 
expected as the timeout is reached). The problem occurs with HTTP commons-
client RC2 and final releases.

A more detailed description:

I seem to get a response code 100 (continue) that's why you can see:

"...HttpMethodBase  - Discarding unexpected response: HTTP/1.1 100 Continue"
(When I use Plain SSL Sockets I do not get this code. I always get the 200 SC.)

The problem is that after the timeout is reached and the server is still 
processing the request, the exception is thrown. From my point of view, 
the "real bug" is the exception message that should indicate that the timeout 
period was reached while awaiting for data and not "there were a problem while 
parsing the HTTP line from the response". From the JavaDoc, the method 
HttpClient.setTimeout says that "it's the timeout for waiting for data" but if 
no data was sent by the target server until the timeout was reached, it should 
warn properly.

Maybe a way to simulate the problem is to create a JSP page that keeps 
processing a long time (Thread.sleep) and we make the request to this JSP 
invoking HttpClient.setTimeout with a low value. This way I think we will be 
able to simulate the problem.

It's too late here (Brazil). Tomorrow morning I'll try to work in a way to 
simulate the problem with the JSP approach.

Thanks a lot for the quick response!
Daniel

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

Reply via email to