IBM Support

IJ02662: TADDM DISCOVERIES VIA ITM MONOPOLISE THE HUB'S SOAP THREADS AND TAKE TOO LONG

A readme is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Discoveries performed through ITM utilise KT1 which issues many
    SOAP requests to query the Hub's Node Status table.
    These requests involve an entire scan of Node Status table
    which can each take a number of seconds to complete if the Node
    Status table is large.
    Due to the high volume of these requests, TADDM discovery
    requests are prolonged and SOAP threads are monopolised
    preventing concurrent tacmds from running.
    

Local fix

  • N/A
    

Problem summary

  • Throughout the course of a TADDM discovery via TEPS, KT1 sends
    many requests to the Hub to obtain the Node Status of agents.
    These requests compete with the actual discovery requests that
    are sent to each agent.  This contention causes the discovery
    requests to wait prolonging the overall time of the discovery.
    The contention also means that concurrent tacmd requests will
    wait until a SOAP thread becomes available.
    
    
    TADDM Discoveries through ITM take too long to complete.  Also,
    during a discovery, tacmd may hang and Hub CPU may increase.
    

Problem conclusion

  • KT1 now supports the caching of Node Status records which
    eliminates > 95% of the requests that are sent to the Hub during
    a discovery.  Caching is enabled when a new environment
    variable, KT1_NODE_STATUS_CACHE_TTL, is defined with a value > 0
    and < 86400 seconds.  A higher TTL value will reduce the number
    of requests sent to the Hub.  A value of 900 seconds is
    recommended. (see Install Actions below)
    
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
       | service pack | 6.3.0.7-TIV-ITM-SP0001
    
    Install Actions:
    
    
    The environment variable, KT1_NODE_STATUS_CACHE_TTL=<#
    of seconds> should be added to the TEPS configuration file:
    
    $CANDLEHOME/config/cq.ini (Unix/Linux)
    %CANDLE_HOME%\CNPS\KFWENV (Windows)
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ02662

  • Reported component name

    TEMA

  • Reported component ID

    5724C04TE

  • Reported release

    630

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-12-14

  • Closed date

    2019-05-06

  • Last modified date

    2019-05-07

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    OA56396

Fix information

  • Fixed component name

    TEMA

  • Fixed component ID

    5724C04TE

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"630","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
08 March 2023