IBM Support

JR48482: EVENT GATEWAY WITH MULTIPLE IMES IGNORES EXISTING DURABLE MESSAGES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a BPD contains an Event Gateway with multiple intermediate
    message
    events that specify 'Durable Subscription' then existing durable
    messages are not delivered to instances of this BPD even if the
    correlation matches.
    

Local fix

  • n/a
    

Problem summary

  • If a BPD contains an Event Gateway with multiple Intermediate
    Message Events that specify 'Durable Subscription' then
    existing Durable Messages are not delivered to instances of this
    BPD even if the correlation matches.
    
    PROBLEM DETAILED DESCRIPTION:
    When a BPD activates during a navigation transaction an Inbound
    Message Event, it - registers this event as waiting event in
    the database (table lsw_inst_msg_incl) - remembers the waiting
    event in the BPD's execution context.
    If an Event Gateway with multiple Intermediate Message Events is
    activated, multiple waiting events are registered in the
    database and in the BPD's execution context.
    When the BPDs navigation transaction ends and one or more
    waiting events are found in the BPDs execution context, then a
    BPDDurableMessageRecheck task is scheduled with the Event
    Manager that checks whether Durable Messages are available and
    delivers them immediately to one or more of the waiting
    Intermediate Message Events. The implementation of the
    BPDDurableMessageRecheck task calls a method, that determines
    which events from the waiting events that were remembered in
    the BPDs execution context are still registered in the
    database. This method has a parameter that determines whether
    all or only the first found waiting event should be returned.
    The value of this parameter was set to return only the first
    found waiting event and if this event does not match the
    availabe Durable Message, the Durable Message is ignored.
    

Problem conclusion

  • Set the parameter so that all waiting events are returned.
    
    FIX AVAILABILITY:
    iFix for 8.0.1.1 is available on Fix Central, search for APAR
    JR48482 at http://www.ibm.com/support/fixcentral/
    iFix for 8.0.1.2 is available on Fix Central, search for APAR
    JR48482 at http://www.ibm.com/support/fixcentral/
    iFix for 8.5.0.1 is available on Fix Central, search for APAR
    JR48482 at http://www.ibm.com/support/fixcentral/
    Fix is also targetted for inclusion in next fixpack for BPM
    8.0.1, BPM 8.5.0
    
    When obtaining any of the above fixes, be sure to download the
    accompanying readme, for itself, and any prerequisite fixes, and
    review them thorougly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR48482

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-11-13

  • Closed date

    2013-12-03

  • Last modified date

    2013-12-03

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

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

Fix information

  • Fixed component name

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R801 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
03 December 2013