IBM Support

PI60120: 0C4 ABEND IN STDDICTIONARYINFO DESTRUCTOR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The following abend stack trace is the result of accessing
    storage in the CacheManager that is no longer valid:
    
    StdDictionaryInfo::¯StdDictionaryInfo()
    RMCacheEntry::¯RMCacheEntry()
    CacheManager::garbageCollect(short)
    ResourceManager::rmFindDictionary(const unsigned short*)
    MtiImbParserFactory::deployedResourceManager(const ImbWstrin
    ImbDeployedResourceGroup::deployedResourceManager(const ImbW
    ImbDataFlowApplication::deployedResourceManager(const ImbWst
    CpContext::loadDictionary(const ImbWstring&)
    CpContext::initialize(MtiImbSyntaxElement*)
    MtiImbParser::loadParserResources()
    
    A review of the nthreads in the abend dump show that multiple
    threads are accessing this storage cell simultaneously, as the
    CacheManager is not thread safe.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Message Broker v8.0 and IBM Integration
    Bus v9.0 and v10.0 using the MRM with additional instances.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    There is a very small timing window such that if multiple
    threads access the MRM dictionary CacheManager at the exact same
    time, an abend with the following trace back stack may occur:
    
    StdDictionaryInfo::¯StdDictionaryInfo()
    RMCacheEntry::¯RMCacheEntry()
    CacheManager::garbageCollect(short)
    ResourceManager::rmFindDictionary(const unsigned short*)
    MtiImbParserFactory::deployedResourceManager(const ImbWstrin
    ImbDeployedResourceGroup::deployedResourceManager(const ImbW
    ImbDataFlowApplication::deployedResourceManager(const ImbWst
    CpContext::loadDictionary(const ImbWstring&)
    CpContext::initialize(MtiImbSyntaxElement*)
    MtiImbParser::loadParserResources()
    
    
    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

    PI60120

  • Reported component name

    WEB MB Z/OS

  • Reported component ID

    5697P4400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-04-04

  • Closed date

    2016-06-14

  • Last modified date

    2016-06-14

  • 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

    5697P4400

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 June 2016