IBM Support

PK88853: A CRASH CAN OCCUR WHEN SENDING THE TERMINATE SIGNAL TO A STATEMACHINE. THIS IS DUE TO A KNOWN ISSUE WITH OMREACTIVE.CP

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible.

Error description

  • handleEventUnderDestruction
    (const IOxfEvent* ev) {
        //#[ operation handleEventUnderDestruction(IOxfEvent)
        if ((ev != NULL) ??
         ev-?isTypeOf(OMReactiveTerminationEventId)) {
         if (shouldDelete()) {
          if (isDestroyEventResent()) {
           // second consumption
           // self termination event - do self destruction
           delete this;
          } else {
           // first consumption - resend
           // When destroy is called the reactive instance is set in
    under destruction mode
           // that prevents sending of additional events and the
    terminate event is sent by the instance to itself.
           // The terminate event must be the last event sent to
    this instance and since the setting in under destruction mode is
    done without guarding                                 // (for
    performance considerations), the terminate event is reset after
    consumed on the first time to avoid a scenario where,
           // due to task scheduling, another event is sent after
    the destroy event.
           // Sending the terminate event a second time prevents
    most scheduling races
           // however it does not prevent all possible scenarios.
           // In case that your scheduler may stop a task in the
    middle of a regular code (without a blocking call)
           // for indefinite time (that will let the reactive
    instance thread dispatch the terminate event twice),
           // you should consider using the direct deletion policy.
           (void) send(?theTerminateEvent);
           setDestroyEventResent();
          }
         }
        }
        return instanceUnderDestruction;
        //#]
    }
    

Local fix

  • N/A
    

Problem summary

  • APAR PK88853 - Rhapsody crashes when statemachine is
    terminted (OMReactive.cpp)
    

Problem conclusion

  • This defect is not reproducible.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK88853

  • Reported component name

    TLOGIC RHAPSODY

  • Reported component ID

    5724V74RP

  • Reported release

    750

  • Status

    CLOSED UR5

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-06-15

  • Closed date

    2009-12-02

  • Last modified date

    2009-12-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R750 PSN

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7P9W","label":"Rational Rhapsody"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
02 December 2009