IBM Support

IZ36038: FDC with Probe ID XC130003 SIGSEGV from WebSphere MQ Extended Transactional Client when called in error from a handler


You can track all active APARs for this component.


APAR status

  • Closed as program error.

Error description

  • Probe Id          :- XC130003
    Component         :- xehExceptionHandler
    Comment1          :- SIGSEGV: address not mapped
    The trace history in the FDC file shows that the WebSphere MQ
    client code was in the middle of a call to the server.  At that
    time it was interrupted and a new call was attempted from
    application code into WebSphere MQ's API.  (The API includes
    calls to WebSphere MQ's XA functions).  This was the sequence:
     -{ MQGET
     --{ MakeCall
     ---{ ccxReceive
     ----{ cciTcpReceive
     -----{ ccxAllocMem
     -----} ccxAllocMem rc=OK
     -----{ recv
     -----} recv rc=Unknown(FFFF)
     -----{ xcsWaitFd
     ------{ poll
     -------{ XAEnd        <--------- New call through MQ's API
     --------{ MakeCall
     ---------{ ccxAllocMem

Local fix

Problem summary

  • ****************************************************************
    Applications using the WebSphere MQ Extended Transactional
    Client that have handlers installed that might get control while
    in the middle of a WebSphere MQ API call.
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows)
    While this interrupting and calling into the API is not correct
    use of WebSphere MQ's API it should still be handled more
    gracefully.  A SIGSEGV should not be generated.  The more
    desirable behaviour is for our xa_end call to fail, returning
    with rc=XAER_PROTO.

Problem conclusion

  • Improved checking has been added to the WebSphere MQ code so
    that incorrect calls through the API (eg. from handlers that get
    control while an existing API call is in progress) are rejected
    with a sensible return code.
    The fix is targeted for delivery in the following PTFs:
    Platform           Fix Pack
    --------           --------------------
    Windows            U200299
    AIX                U819350
    HP-UX (PA-RISC)    U819028
    HP-UX (Itanium)    U819230
    Solaris (SPARC)    U819232
    Solaris (x86-64)   U819240
    iSeries            tbc_p600_0_2_6
    Linux (x86)        U818989
    Linux (x86-64)     U819234
    Linux (zSeries)    U819231
    Linux (Power)      U819029
    Linux (s390x)      U819233
    Platform           Fix Pack
    --------           --------------------
    Windows            U200302
    AIX                U822354
    HP-UX (PA-RISC)    U822349
    HP-UX (Itanium)    U822351
    Solaris (SPARC)    U822353
    Solaris (x86-64)   U822394
    iSeries            tbc_p700_0_0_2
    Linux (x86)        U822348
    Linux (x86-64)     U822393
    Linux (zSeries)    U822352
    Linux (Power)      U822350
    The latest available maintenance can be obtained from
    'Websphere MQ Recommended Fixes'
    If the maintenance level is not yet available, information on
    its planned availability can be found in 'Websphere MQ
    Planned Maintenance Release Dates'

Temporary fix


APAR Information

  • APAR number


  • Reported component name

    WMQ LIN X86 V6

  • Reported component ID


  • Reported release


  • Status


  • PE




  • Special Attention


  • Submitted date


  • Closed date


  • Last modified date


  • 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


Applicable component levels

  • R600 PSY


[{"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:
10 March 2009