IBM Support

PM86255: ADMIN AGENT ABENDS WHEN PROCESSING A CHANGE RESPONSE FOR A BROKER WITH LOTS OF EXECUTION GROUPS AND MESSAGE FLOWS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An abend of the Admin Agent process is observed when updating
    the
    deployment log after a change request is issued on a broker
    which has many execution groups and message flows.
    In this instance the customer issued the mqsichangeflowstats
    command to enable stats for all message flows in all
    execution groups. This generated over 2000 deployment log
    entries which were not handled correctly by the Admin Agent.
    An abend stack similar to this may be observed:
    
    ImbDeployManagerCache::addLogEntries(std::vector<ImbWstring,
    ImbDeployManagerCache::refresh(ImbQueueManager&)
    ImbDeployManagerCacheRefreshThread::refreshCache(ImbQueueMan
    ImbDeployManagerCacheRefreshThread::run(ImbOsThread*)
    ImbThreadPoolThreadFunction::run(ImbOsThread*)
    ImbOsThread::innerThreadBootStrapWrapper(void*)
    ImbOsThread::threadBootStrap(void*)
    threadBootStrapWrapper
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Message Broker V7.0 and V8.0 or IBM
    Integration Bus V9.0 who have a very large number of execution
    groups and message flows deployed to a single broker.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    An abend of the admin agent process is observed when updating
    the administration log after a change request is issued on a
    broker which has many execution groups and message flows. In
    this instance the mqsichangeflowstats command was issued to
    enable stats for all message flows in all execution groups. This
    generated over 2000 deployment log entries which were not
    handled correctly by the admin agent. An abend stack similar
    to this may be observed:
    
    ImbDeployManagerCache::addLogEntries(std::vector<ImbWstring,
    ImbDeployManagerCache::refresh(ImbQueueManager&)
    ImbDeployManagerCacheRefreshThread::refreshCache(ImbQueueMan
    ImbDeployManagerCacheRefreshThread::run(ImbOsThread*)
    ImbThreadPoolThreadFunction::run(ImbOsThread*)
    ImbOsThread::innerThreadBootStrapWrapper(void*)
    ImbOsThread::threadBootStrap(void*)
    threadBootStrapWrapper
    

Problem conclusion

  • The product now correctly handles the update of the
    administration log when it receives more results from one
    deployment action than the maximum capacity of the log.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following:
    
    Version            v9.0
    --------           --------------------
    Fix available in:  9.0.0.1
    
    Version            v7.0
    --------           --------------------
    Fix available in:  7.0.0.7
    
    Version            v8.0
    --------           --------------------
    Fix available in:  8.0.0.3
    
    The latest available maintenance can be obtained from
    'WebSphere Message Broker Recommended Fixes'
    http://www.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 in 'WebSphere Message
    Broker Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM86255

  • Reported component name

    WEB MB Z/OS

  • Reported component ID

    5655V6000

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-03

  • Closed date

    2013-07-29

  • Last modified date

    2013-07-29

  • 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

    WEB MB Z/OS

  • Fixed component ID

    5655V6000

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"7.0"}]

Document Information

Modified date:
01 November 2021