[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The length requested for storage allocation is out of range



The error is occurring in http_url_post_xml. Here's the statement that
I'm using - cTimeOut is set at 600. Could that be the problem - I'm not
giving enough time to receive the entire response? The response of this
web service can be pretty slow.

rc = http_url_post_xml(                             
    'https://ws.labone.com/services/eoservice.asmx' 
          : %addr(SOAP)+2                           
          : %len(SOAP)                              
          : *NULL                                   
          : %paddr(EndOfElement)                    
          : *NULL                                   
          : cTimeOut);                              

Here's the first page of the dump - 

ILE RPG FORMATTED DUMP

Program Status Area:

Procedure Name . . . . . . . . . . . . :   WEB397

Program Name . . . . . . . . . . . . . :   WEB397

   Library . . . . . . . . . . . . . . :   WEBLIB

Module Name. . . . . . . . . . . . . . :   WEB397

Program Status . . . . . . . . . . . . :   00202

             The call to  ended in error (C G D F).

Previous Status  . . . . . . . . . . . :   00000

Statement in Error . . . . . . . . . . :   00007534

RPG Routine  . . . . . . . . . . . . . :   HTTP_URL

Number of Parameters . . . . . . . . . :   003

Message Type . . . . . . . . . . . . . :   RNX

Additional Message Info  . . . . . . . :   0425

Message Data . . . . . . . . . . . . . :

             The length requested for storage allocation is out of
range.
Status that caused RNX9001 . . . . . . :

Last File Used . . . . . . . . . . . . :    

                             
The first time this error occurred the content-length was 10833517, and
only 9846465 was received. The second time it happened the
content-length was 10164047, and 9857785 was received (I isolated the
response portion of each debug file into a text file to determine the
size of the response received).

I'm only keeping a week's worth of debug logs, but the next largest
content-length I've received was 5921033, and it was received in its
entirety without a problem. So I guess I'm assuming it's erroring out
whenever I receive a response of a certain size.

As for reproducing the problem - I suppose I could send you the response
that I have in the debug file with the identifying information removed,
and I can doctor it up so that it is the correct content? Would that
help? 

Thanks so much,

Kim

----------------------------------------------------------------------

>From: Scott Klement <sk@xxxxxxxxxxxxxxxx>
>Subject: Re: The length requested for storage allocation is out of
>
>Hi Kim,
>
>All I know about this problem at this point is that you're receiving an

>XML document with length 10164047, and it somehow results in a "length 
>of storage allocation out of range".
>
>Which routine in HTTPAPI are you calling?  Can you tell me how to 
>reproduce the problem?  Does it occur every time you download an XML 
>document of a certain size?
>
>
>
>
>
>
>>On 6/6/2011 9:34 AM, Kim Mitchell wrote:
>> Hello Scott,
>>
>> Thanks for the response. I've looked at file CHANGELOG, and it
appears
>> we're using version 1.24 Beta 11. We upgraded in mid-February, and
the
>> upgrade fixed a few issues. This problem just started last week.
>>
>> Kim
>>
>>> ------------------------------
>>> Date: Fri, 03 Jun 2011 17:10:03 -0500
>>> From: Scott Klement<sk@xxxxxxxxxxxxxxxx>
>>> Subject: Re: The length requested for storage allocation is out of
>>> 	range
>>>
>>> Hi Kim,
>>>
>>> What version of HTTPAPI?  I suspect this is an issue that was fixed
in
>>> 1.24beta11.  Make sure you're running that version (or newer).
>>>
>>> Thanks.

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------