IBM Support

JR52069: DURABLE MESSAGES ARE NOT DELIVERED TO ALL INSTANCES OF AN INTERMEDIATE MESSAGE EVENT IN A MULTI-INSTANCE LOOP

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If an intermediate receive message event that has the Durable
    Subscription option selected  and the Consume Message option
    cleared is in a multi-instance loop, the durable message is not
    delivered to all instances of the event.
    
    If the message is received before the multi-instance loop is
    activated, it is only delivered to one instance of the message
    event. If the multi-instance loop is activated before the
    message is received, the message is delivered to all message
    events in a waiting state but not to intermediate message events
    that are activated after the message is received.
    

Local fix

Problem summary

  • If multiple instances of a multi-instance loop that have an
    intermediate message event are activated, each instance of the
    intermediate message event has the same event ID. IBM BPM
    assigns a unique wait ID to each instance of the intermediate
    message event, but this wait ID is not reflected correctly in
    the query that determines whether a durable message is available
    when an intermediate message event is activated. Therefore, IBM
    BPM concludes that the message has already been delivered if the
    second or third instance of an intermediate message event is
    activated.
    

Problem conclusion

  • A fix is/will be available for IBM BPM V8.0.1.1 that modifies
    the <find-durable-messages-for-event-query> so that it reflects
    the wait ID when it checks whether a durable message is
    available for an intermediate message event.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR52069:
    
    1. Select IBM Business Process Manager with your edition from
      the product selector, the installed version to the fix pack
      level, and your platform, and then click Continue.
    
    2. Select APAR or SPR, enter JR52069, and click Continue.
    
    When you download fix packages, ensure that you also download
    the readme file for each fix. Review each readme file for
    additional installation instructions and information about the
    fix.
    

Temporary fix

  • Not applicable
    

Comments

APAR Information

  • APAR number

    JR52069

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-12-15

  • Closed date

    2015-02-13

  • Last modified date

    2015-02-13

  • 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

[{"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:
13 February 2015