Get Request fails when response id greater than int.

Lawrence Schapker <[email protected]>
Newsgroups gmane.comp.java.grinder.user
Message-ID <[email protected]>
Hello All,

Hope everyone is having a joyous holiday!

I just stumbled onto an issue and was wondering if anyone else has seen
this.  If so, how they handled the situation.

I'm making a streaming get request that that will receive a file that can be
huge (can be more than 3 GB).  If the response size is less than 2 GB (i.e.
less than the maximum int value), all is fine.  If the file is larger than
the maximum int value, I receive the following error:

"java.net.ProtocolException: Invalid Content-length header received:
2160763944"

Please note that the "2160763944" is the size of the file being downloaded
(and it is larger than a int can hold)

I find that the issue is within the "Response.java" and my error is
generated from ~ line 734.

I suspect that the "fix" may be more than just changing the local variable
from a int to a long.  I'm guessing that many places throughout the
HTTPClient code deck will require some refactoring to work properly.

Short of "make the file smaller", any suggestions as to how to proceed?

Thank you,

Larry Schapker
Senior IT Performance Engineer
Salesforce.com



--
View this message in context: http://grinder.996249.n3.nabble.com/Get-Request-fails-when-response-id-greater-than-int-tp8725.html
Sent from the Grinder - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.