IBM Support

IT09838: MQBEGIN FAILS WITH MQRC 2128 IN TIMEOUTNOTIFICATION NODE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • A globally coordinated message flow containing a
    TimeoutNotification node continuously reports MQBEGIN failures
    with a return code of 2128 (MQRC_UOW_IN_PROGRESS). This can
    happen when a message flow containing a TimeoutNotification
    node is started AND it finds timeout requests in its
    internal timeout store that are now expired AND the
    IgnoreMissed property is set to True. These messages do not get
    propagated out of the node, and as a result no MQCMIT is issued
    to end the unit of work.
    

Local fix

  • <html>none
    </html>
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v9.0 and v10.0 using the
    TimeoutNotification node in a globally coordinated message flow.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A globally coordinated message flow containing a
    TimeoutNotification node continuously reports BIP2605E MQBEGIN
    failures with a return code of 2128 (MQRC_UOW_IN_PROGRESS). This
    can happen when a message flow containing a TimeoutNotification
    node is started and it finds timeout requests in its internal
    timeout store that are now expired and the IgnoreMissed property
    is set to True.
    These messages do not get propagated out of the node, and as a
    result no commit is issued to end the unit of work.
    
    
    <i>There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0. For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm</i>
    

Problem conclusion

  • The TimeoutNotification node now ends the unit of work after an
    expired timeout message is processed without propagation.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0       9.0.0.6
    v10.0      10.0.0.4
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT09838

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-07-03

  • Closed date

    2016-03-07

  • Last modified date

    2016-03-07

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0530

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020