IBM Support

IT22461: TIMEOUTNOTIFICATION NODE MAY DELAY SENDING SOME EVENTS AFTER AN MQSIRELOAD COMMAND

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 TimeoutNotification node is processing and sending
    notification messages for a Timeout request.
    
    A new Timeout request message is received with the
    'AllowOverwrite' value set to 'true'.
    
    However the TimeoutNotification node may continue sending
    timeout notifications related to the previous Timeout request
    for the same Timeout identifier, before changing over to the new
    Timeout request message settings.
    
    In this case the TimeoutNotification node is expected to ignore
    the previous Timeout request message and should start processing
    the new Timeout request message immediately.
    
    The problem is more likely to occur after an Integration Server
    restart or reload, when the 'IgnoreMissed' property of the
    existing Timeout request is set to 'False'.
    
    In this scenario, if a new Timeout request arrives while the
    TimeoutNotification node is still processing missed timeouts
    from the restart or reload, then  a duplicate Timeout request
    message may be put to the SYSTEM.BROKER.TIMEOUT.QUEUE for the
    same Timeout Identifier.
    
    Additional Symptom(s) Search Keyword(s):TimeoutNotification,
    Controlled mode, timeout intervals, timeouts, TimeoutControl
    

Local fix

  • The problem is reduced, to some extent, if control events
    created by the TimeoutControl with short timeout intervals, are
    prioritised ahead of events which have longer timeout intervals.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise v11.0 and IBM
    Integration Bus v10 using the TimeoutNotification node.
    
    
    Platforms affected:
    MultiPlatform, z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A TimeoutNotification node is processing and sending
    notification messages for a Timeout request.
    
    A new Timeout request message is received with the
    'AllowOverwrite' value set to 'true'.
    
    However the TimeoutNotification node may continue sending
    timeout notifications related to the previous Timeout request
    for the same Timeout identifier, before changing over to the new
    Timeout request message settings.
    
    In this case the TimeoutNotification node is expected to ignore
    the previous Timeout request message and should start processing
    the new Timeout request message immediately.
    
    The problem is more likely to occur after an Integration Server
    restart or reload, when the 'IgnoreMissed' property of the
    existing Timeout request is set to 'False'.
    
    In this scenario, if a new Timeout request arrives while the
    TimeoutNotification node is still processing missed timeouts
    from the restart or reload, then  a duplicate Timeout request
    message may be put to the SYSTEM.BROKER.TIMEOUT.QUEUE for the
    same Timeout Identifier.
    

Problem conclusion

  • The product now prevents delays in sending a timeout
    notification for a new Timeout request  after a reload or
    restart of an Integration Server.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.13
    v11.0      11.0.0.1
    
    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

    IT22461

  • 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

    2017-09-20

  • Closed date

    2018-06-15

  • Last modified date

    2018-06-15

  • 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:
15 June 2018