hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 31246] - JVM bug 4949631 causes BufferOverflowException in HttpMethodBase.getResponseBodyAsString
Date Thu, 16 Sep 2004 09:51:21 GMT
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=31246>.
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=31246

JVM bug 4949631 causes BufferOverflowException in HttpMethodBase.getResponseBodyAsString





------- Additional Comments From afrancis@thoughtworks.com  2004-09-16 09:51 -------
Hi Guys,

I don't agree that the bug is invalid (of course thats up to you :-).  

If the method doesn't work for large responses, I'd expect to see Ortwin's
suggestions of a log message as described below and something in the
documentation referring to the sun bug report and warning of undefined behaviour
if the response is over 16Mb.  What would be safer (IMO) is fail-fast with some
kind of ResponseTooLargeException (or something).

As for our specific situation, it's a safe bet our responses will be 5-20Mb and
so I'll take the advice and go ahead and use the Stream method, if I happened to
be in a situation where I had no idea how big the response was before I tried to
get it, it seems a little worrying that a perfectly reasonable-looking method
might fail at random intervals.

Alan

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org


Mime
View raw message