IBM Support

IT17711: AGGREGATION STATISTICS INCORRECT FOR TIMEOUT THREADPOOL

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

  • If the AggregateReply node is used with a thread pool of
    timeout threads and Accounting and Statistics is enabled then
    the elapsed time can be over-reported by 5 seconds up to once
    per timeout processed.
    
    The issue is caused by starting the timer before issuing an MQ
    GET using a wait option of 5 seconds. In the case where a
    timeout has just been processed and another message does not
    arrive the wait time is included in the elapsed time even
    though the thread is only waiting for work to arrive.
    

Local fix

  • Setting the env var MQSI_AGGR_WAIT_TIMEOUT controls the length
    of this timeout in ms, reducing this to a smaller value such as
    100 reduces the margin by which the elapsed time is
    over-reported.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration bus version 9 or higher using the
    Aggregation nodes.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If the AggregateReply node is used with a thread pool of timeout
    threads and Accounting and Statistics is enabled then the
    elapsed time can be over-repoted by 5 seconds up to once per
    timeout processed.
    
    The issue is caused by starting the timer before executing an MQ
    GET using a wait option of 5 seconds. In the case where a
    timeout has just been processed and another message does not
    arrive the wait time is included in the elapsed time even though
    the thread is only waiting for work to arrive.
    
    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

Temporary fix

Comments

APAR Information

  • APAR number

    IT17711

  • 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-27

  • Closed date

    2017-09-06

  • Last modified date

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

    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