Kbase P128400: Crash at the end of a READ-RESPONSE trigger when logging ProEvents
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/12/2009 |
|
Status: Unverified
SYMPTOM(s):
Crash at the end of a READ-RESPONSE trigger when logging ProEvents
Crash at the end of the execution of a trigger for the READ-RESPONSE event
Log entry types include ProEvents.* logging
Logging level 2 or higher
Issue does not happen if logging is disabled
FACT(s) (Environment):
OpenEdge 10.x
All Supported Operating Systems
CAUSE:
Bug# OE00164148
CAUSE:
This is a known issue. When logging of types ProEvent.* is turned on, the session crashes when logging the end of a READ-RESPONSE trigger, if the socket is deleted (e.g. DELETE OBJECT SELF)
If the socket is deleted in READ-RESPONSE handler (e.g. DELETE OBJECT SELF), the uic is no longer valid. In rnUITProEventLog, the uic is checked for the type so we can display the appopriate type info in the PROEVENTS message. If the uic is not valid, ait is set to null. However, further down in the function puic is dereferenced without checking whether it is null. The same dereferencing is done in umEnhLogEvents without checking if the uic is null.
FIX:
Upgrade to 10.2B where this issue has been addressed by adding checks for a null puic in rnUITProEventLog and umEnhLogEvents.
To workaround the issue, disable logging or remove ProEvents from the log entry types.