Kbase P119050: AppServer with 4GLTrace logentrytype and logginglevel >2 core dumps with rnExecLogParmString
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/01/2009 |
|
Status: Verified
SYMPTOM(s):
4GLTrace logentrytype and logginglevel >2 core dumps with rnExecLogParmString
SYSTEM ERROR: sizditm -- invalid type. (51)
** Save file named core for analysis by Progress Software Corporation. (439)
Error receiving Web Service Response: (11773)
Stack trace from _proapsv reads: (associated with error 51)
sizditm
copditm_nofatal
rnExecLogParmString
rn4GLTraceReturn
rnrunRPCTraceReturn
Sometimes the AppServer will receive error 49
SYSTEM ERROR: Memory violation. (49)
Stack trace from _proapsv reads: (associated with error 49)
__libc_sigaction
rnExecLogParmString
rn4GLTraceReturn
rnprocTraceReturn
rniproc_retn
AppServer core dumps intermittently
-logginglevel set to anything equal or larger than 3 and -logentrytypes set to 4GLTrace
FACT(s) (Environment):
4GLTRACE logging is enabled on the AppServer
All Supported Operating Systems
OpenEdge 10.x
CAUSE:
Bug# OE00123759
CAUSE:
When a RETURN ERROR from a procedure happens, the list of output parameters is not getting properly populated on the stack and rnExecLogParmString did not expect NULL values for the output parameters.
FIX:
The fix is so that if a parameter's ditem is NULL, it will be skiped. This fix exists in OpenEdge 10.1B and later.
As a workaround, use the logging level to 2 instead of 3 or 4.