IBM Support

IT25415: ABEND ON COMMIT WHEN USING MQTTSUBSCRIBE NODE AND USER EXITS.

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

  • Desc: When a user exit is installed on an EG, if the input flow
    starts from an MQTTSubscribe node then the ExecutionGroup will
    abend when transaction comit occurs. The abend stack will
    contain the following function call sequence near the top of the
    stack:
    
    ImbMessage::group()
    ImbCciUserExit::transactionCommitEvent(ImbDataFlowNode
    ImbUserExitManager::transactionCommitEvent(ImbDataFlowNode
      const&, ImbMessage const&)
    ImbCallableTemplateNode::completeDeferredCommit_Type3
      (ImbCallableTemplateNode::ExecutionInstance&)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of the MQTTSubscribe node who have C UserExits active.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a user exit is installed on an Integration Server, if the
    input flow starts from an MQTTSubscribe node then the
    ExecutionGroup will  abend when transaction commit occurs.
    
    The abend stack will contain the following function call
    sequence near the top of the stack:
    
    ImbMessage::group()
    ImbCciUserExit::transactionCommitEvent(ImbDataFlowNode
    ImbUserExitManager::transactionCommitEvent(ImbDataFlowNode(
    const&, ImbMessage const&)
    ImbCallableTemplateNode::completeDeferredCommit_Type3
    (ImbCallableTemplateNode::ExecutionInstance&)
    

Problem conclusion

  • The product no longer abends on commit when a user exit is
    active and the flow starts from an MQTTSubscribe Node.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.14
    v11.0      11.0.0.2
    
    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

    IT25415

  • 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

    2018-06-20

  • Closed date

    2018-09-19

  • Last modified date

    2018-09-19

  • 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

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

Document Information

Modified date:
19 September 2018