IBM Support

IT37207: MQINPUT NODE CONFIGURED WITH ORDER MODE VALUE AS 'BY USER ID' MAY CAUSE DEADLOCK

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

  • MQInput node may get into a deadlock when it is configured with
    order mode property as 'By User ID'. The issue happens when the
    execution goes into the following path:
    1. An exception thrown from the flow causes a rollback of the
    transaction and the message is rolled back to the input queue.
    
    2. The rolled back message is picked again and propagated to the
    failure terminal as the backout count is exceeded.
    
    
    Once the issue hits, the MQInput node fails to pick further
    messages and it will need a restart of the message flow to
    recover.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All Users of IBM App Connect Enterprise V12, V11 and IBM
    Integration Bus V10 using MQInput node's order mode property
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    MQInput node may get into a deadlock when it is configured with
    order mode property as 'By User ID'. The issue can happen when
    the message flow goes through the following execution path:
    
    1. An exception thrown from the flow causes a rollback of the
    transaction and the message is rolled back to the input queue.
    
    2. The rolled-back message is picked again and propagated to the
    failure terminal as the backout count is exceeded.
    
    Once the issue hits, the MQInput node fails to pick further
    messages and it will need a restart of the message flow to
    recover
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT37207

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-06-10

  • Closed date

    2021-08-31

  • Last modified date

    2021-10-06

  • 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

    5724J0540

Applicable component levels

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

Document Information

Modified date:
13 October 2021