IBM Support

IY95706: SIGSEGV IMMEDIATELY FOLLOWING RETURN FROM ZFUDOESOBJECTEXIST XC130004 from amqzlaa0, amqrmppa, or amqfcxba.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • There is a bug in function zfuDoesObjectExist which
    is causing the stack to be corrupted.
    
    A SIGSEGV immediately following return from this
    function results from the stack having been corrupted.
    
    The MQM Function stack will look like:
    kqiAuthorityChecks
    gpiCheckObjectAuthority
    zfu_as_checkobjectauthority
    zfu_as_calculateauthority
    xcsFFST
    
    The tail of the trace history will look like:
    -------------{ zfu_as_calculateauthority
    --------------{ zfu_as_searchprincipallist
    ---------------{ zfuLockHashTable
    ----------------{ xcsRequestMutexSem
    ----------------} xcsRequestMutexSem rc=OK
    ---------------} zfuLockHashTable rc=OK
    ---------------{ zfuLocatePrincipal
    ----------------{ zfuHash
    ----------------} zfuHash rc=OK
    ---------------} zfuLocatePrincipal rc=OK
    ---------------{ zfuUnlockHashTable
    ----------------{ xcsReleaseMutexSem
    ----------------} xcsReleaseMutexSem rc=OK
    ---------------} zfuUnlockHashTable rc=OK
    --------------} zfu_as_searchprincipallist rc=OK
    --------------{ zfuLockHashTable
    ---------------{ xcsRequestMutexSem
    ---------------} xcsRequestMutexSem rc=OK
    --------------} zfuLockHashTable rc=OK
    --------------{ zfuLocateObject
    ---------------{ zfuHash
    ---------------} zfuHash rc=OK
    --------------} zfuLocateObject rc=zrcF_NOT_FOUND
    --------------{ zfuUnlockHashTable
    ---------------{ xcsReleaseMutexSem
    ---------------} xcsReleaseMutexSem rc=OK
    --------------} zfuUnlockHashTable rc=OK
    --------------{ zfuDoesObjectExist
    --------------} zfuDoesObjectExist rc=OK
    --------------{ xcsFFST
    
    Typically an amqzlaa0 process (or possibly an amqrmppa process
    for customers exploiting MQIBindType=FASTPATH, or possibly an
    amqfcxba process) will raise an XC130004 FDC and the amqzlaa0
    process will end. The abrupt termination of the
    amqzlaa0/amqrmppa/amqfcxba process might cause the queue
    manager to crash, depending upon what other threads of that
    agent were doing at the time of the failure.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    
    
    Platforms affected:
     All Distributed (iSeries, all Unix and Windows)
    ****************************************************************
    PROBLEM SUMMARY:
    The OAM occasionally makes a request to the object catalog to
    check the existence of an object. The DAP doesn't actually
    support a 'does this object exist' call and so the OAM makes an
    inquiry to find the real name of the object. This call passes a
    1 byte buffer (expecting to get a buffer too small error to
    imply the existence of the object). When the DAP is able to
    find the object name in a cache it was not checking the caller
    had supplied a big enough buffer and was therefore overwriting
    the stack.
    

Problem conclusion

  • Added the appropriate length check.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v5.3
    Platform           Fix Pack 14
    --------           --------------------
    Windows            U200266
    AIX                U808477
    HP-UX (PA-RISC)    U808478
    Solaris (SPARC)    U808480
    iSeries            SI24366
    Linux (x86)        U808481
    Linux (zSeries)    U808483
    
                       v6.0
    Platform           Fix Pack 6.0.2.2
    --------           --------------------
    Windows            U200270
    AIX                U809895
    HP-UX (PA-RISC)    U809898
    HP-UX (Itanium)    U810084
    Solaris (SPARC)    U809913
    Solaris (x86-64)   U810362
    iSeries            SI27286
    Linux (x86)        U809950
    Linux (x86-64)     U810178
    Linux (zSeries)    U810081
    Linux (Power)      U810083
    Linux (s390x)      U810110
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available, information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IY95706

  • Reported component name

    WMQ LIN X86 V6

  • Reported component ID

    5724H7204

  • Reported release

    600

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-03-07

  • Closed date

    2007-03-28

  • Last modified date

    2007-07-27

  • 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

    WMQ LIN X86 V6

  • Fixed component ID

    5724H7204

Applicable component levels

  • R600 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ5M","label":"APAR"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
27 July 2007