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

Re: HELP HELP HELP - Invalid heap space using HTTPAPI



Julio and Mike,

Although it is eXpat that actually sends the error message it must not 
necessarily be responsible for the error.

Julio:

a) Are you using dynamic memory allocation in your program?
b) Are you using memcpy() or any other C function to copy memory blocks?
c) Are you using OPTION(*NOPASS) in your programs?
d) Are you using OPTION(*VARSIZE) in your programs?

All of these things might be responsible for the error because it is 
possible to accidentally corrupt memory blocks outside the current scope, e.g.:

a) Perhaps you allocated to less memory and changed memory outside the 
allocated boundary.

b) Perhaps you specified a length beyond the intended length when using 
memcpy().

c) Perhaps you did not carefully check the number of parameters passed to 
your program and changed a variable which had not been passed. Very common 
error that often happened on our side. :-( I am looking forward to 
%PARMNUM() in V7R1.

d) Perhaps you changed a fixed length variable beyond the length passed to 
the program.

The problem with all these errors is that you do not immediately get an 
error. Often the the program crashes far later and therefore the statement, 
which is responsible for the error, is difficult to find.

Thomas.


Am 04.02.2011 01:36, schrieb Mike Krebs:
> Julio,
>
> The joblog indicates the error is within EXPAT. I am not sure if the version included in LIBHTTP is the latest. EXPAT looks to be stable with no releases since 2007 but you could check if there are newer versions. There are a few bug reports regarding memory leaks, but I didn't run across anything specific to your error (which appears to be a dealloc related error).
>
> If fixing EXPAT is not within your abilities...workarounds to consider.
>
> 1. Use native XML support to do the parsing.
> 2. Since you indicate a restart fixes...Build the process to restart the service every x emails.
>
>
>> Mike:
>>
>> It is happening once or twice a week in a program that read information
>> from a file and write another file and is getting information about the
>> member email using a module GETEMAIL which consume a Web service from a
>> main server.It had happened also in other programs with different Web
>> Services, but always when a large number of records are processed. With
>> 2,000 or 3,000 records it do not happens.
>>
>> El Web server en SOAPUI is attached as getEmail-request.txt and the
>> answer
>> as getEmailresponse.txt
>>
>> Too many times yesterday was 45,720 times.
>>
>> We have to cancel the process, see in what record happened and restart
>> a
>> new session from there.
>>
>>
> ---------
>
>
>
>
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------