IBM Support

JR48550: DURABLE MESSAGES CAN BE DELIVERED TO MESSAGE EVENT MORE THAN ONCE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a BPD contains an attached intermediate message event with
    the 'Repeatable' flag and the 'Durable Subscription' flag and
    the 'Consume Message' flag checked, and multiple messages are
    sent to this BPD in a short time, then some of these message can
    be delivered multiple times.
    

Local fix

Problem summary

  • Durable messages can be delivered to message event more than
    once
    
    PROBLEM DETAILED DESCRIPTION:
    If multiple durable messages arrive in a short time for an
    attached message event with the 'interrupt activity' flag
    unchecked, the 'repeatable' flag checked and the 'consume
    message' flag checked, it can happen that some of these
    messages are delivered multiple times.
    The reason is that handling of durable messages is difficult,
    since events that are activated check whether there is a
    durable message that they could consume and on the other hand,
    messages arriving check whether there is a waiting message
    event to which they could be delivered. To find out, whether a
    durable message has already been delivered to a BPD instance,
    the <is-message-consumed-query> checks the database. This query
    did not catch all cases in which a durable message event was
    already delivered to a BPD instance. Especially, if a message
    event waits with a wait id, but the durable message was
    delivered to a different wait id of the same message event in
    the BPD instance, the query did not discover that the message
    was already delivered.
    

Problem conclusion

  • Fix the <is-message-consumed-query>. Now the query discovers
    that the message is already delivered to a BPD instance, even
    if it was delivered to a different wait id.
    
    FIX AVAILABILITY:
    iFix for 8.0.1.2 is/will be available on Fix Central; search for
    APAR JR48550 at http://www.ibm.com/support/fixcentral/
    iFix for 8.5.0.1 is/will be available on Fix Central; search for
    APAR JR48550 at http://www.ibm.com/support/fixcentral/
    Fix is also targetted for inclusion in next fixpack for
    BPM V7.5.1, BPM 8.0.1
    
    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

    JR48550

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-11-20

  • Closed date

    2014-02-18

  • Last modified date

    2014-02-18

  • 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":"7.5.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 February 2014