IBM Support

IT17526: FAIL TO WRITE AGGREGATE REPLIES LEAVES STUCK MSGS ON REQUEST Q

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

  • In the Aggregate Reply node, if a failure occurs when writing
    messages to the AggregateReply queue then a stranded message can
    be left
    on the Aggregate Request queue.
    
    If the "Unknown Message Timeout" property on the
    AggregateRequest Node is set to anything other than 0 then these
    messages will be
    cleaned up automatically.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus using the Aggregation Nodes.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    In the Aggregate Reply node, if a failure occurs when writing
    messages to the AggregateReply queue then a stranded message can
    be left on the Aggregate Request queue.
    
    If the "Unknown Message Timeout" property on the
    AggregateRequest Node is set to anything other than 0 then these
    messages will be  cleaned up  automatically.
    
    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
    

Problem conclusion

  • An environment variable MQSI_AGGR_REQUEST_TIMEOUT_FACTOR has
    been introduced. When set to a positive integer this sets the
    expiry on the internal aggregate request messages to this
    multiple of the aggregation expiry.
    
    So for example if the aggregation timeout is set to 10 seconds
    and the aggregate request timeout factor is set to 5 then the
    request messages will have an expiry of 50 seconds.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.8
    v9.0       9.0.0.8
    
    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

    IT17526

  • 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

    2016-10-17

  • Closed date

    2017-03-15

  • Last modified date

    2017-03-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

    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