I got another OutOfMemory error, and I think it's because the connection (or the method) is keeping a handle on what data is retrieved, and then it fails while trying to get the content-length to read the headers. Check out these (believed) bugs in the code...
HttpMethodBase Line 1055: calls getResponseHeader with "Content-Length"... should be "content-length" since getResponseHeader returns all lower case HttpMethodBase Line 1056: same thing, different header HttpMethodBase Line 454: same thing, different header GetMethod Line 387: same thing, Content-Length again, and I think the source of my problem So, I would guess that the GetMethod is failing to get the expectedLength Then it tries to parse the response and for whatever reason, the server does not stop sending data when it should. readResponseBody continues until it runs out of memory. Other notes for the record... this is on Win 2k w/256 megs RAM, mx size of 128 megs, the temp file that remained after the OutOfMemory was 128 megs (the coincidence peaked my curiosity), it retrieved 76738 jpeg responses successfully for about 1.9 gigs, and ran for about 47 hours before crashing. This is actually the longest it had run before getting the OOM error. Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
