Bug 178445
Summary: | java.net.ProtocolException | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andrew Overholt <overholt> | ||||||
Component: | gcc | Assignee: | Tom Tromey <tromey> | ||||||
Status: | CLOSED RAWHIDE | QA Contact: | |||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | rawhide | CC: | ifoox, jakub, patrickm, tromey | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2006-01-23 18:36:12 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Andrew Overholt
2006-01-20 17:03:55 UTC
Created attachment 123493 [details]
Test case (ripped out of eclipse{,-bugzilla})
Created attachment 123502 [details]
explanation
I think what was happening previously was that the http protocol handler was eagerly reading the entire response body into a byte[]. This meant that we didn't have to handle flushing the body anywhere else. Testing a patch. As Andrew said in the original report we were trying to reproduce another bug in which the connection timed out, so if the patch fixes this, it might trigger the other bug. Unless they are related of course. I've checked in the fix to gcc cvs, on the 4.1 branch. It is purely a libgcj change and won't require any application rebuilds. Even with the patch, the attached test case fails -- it times out when reading. However, if I comment out the call to getTimedInputStream (so that we're reading from the raw un-timed-out underlying input stream), then it works. I suspect that there is a timing bug of some kind in the timed input stream code, but I have not looked into it deeply. Thanks a lot for the quick fix! The timeout bug is the one we were originally after. Now we can try and dig out the timeout bug. I have verified that the first bug is indeed fixed. I have opened a new one for the timeout: bug 178703. Thanks! |