IBM Support

IT29695: SIGSEGV within function rfxAddCLQ and queue manager will not start

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A failure data capture (FDC) record with the following pattern
    is written:
    
    Probe Id :- XC130004
    Component :- xehExceptionHandler
    Program Name :- amqzxma0
    Major Errorcode :- STOP
    Arith1 :- 11 (0xb)
    Comment1 :- SIGSEGV: address not mapped
    
    O/S Call Stack for current thread includes the following (some
    of the numbers might differ from those given below):
    
    /opt/ibm/mqm/lib64/libmqmcs_r.so(xehExceptionHandler+0x104e)
    /lib64/libpthread.so.0
    /lib64/libc.so.6(memcpy+0xd2)
    /opt/ibm/mqm/lib64/libmqmr_r.so(rfxAddCLQ+0x904)
    /opt/ibm/mqm/bin/amqzxma0[0x41a59a]
    
    MQM Function Stack
    ExecCtrlrMain
    zxcStartupLogic
    zxcPostInitialiseSetup
    zxcCreateRepositoryCache
    zxcRestoreCache
    zxcRestoreObject
    zxcRestoreObjectClq
    rfxAddCLQ
    xcsFFST
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of MQ clusters.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A pointer variable was being used in an uninitialised state in
    the case where an internal clustering "CLQ" record has no
    "CLQCLUS" records.  In this seemingly rare case, the
    uninitialised pointer variable contained a value that was not
    null, but was not a valid pointer.  Therefore this condition
    caused a SIGSEGV under rfxAddCLQ.  In turn this prevented the
    Queue Manger from starting.
    

Problem conclusion

  • The pointer variable is now properly initialised in all cases,
    so this problem is permanently avoided.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.13
    v9.0 LTS   9.0.0.8
    v9.1 CD    9.1.4
    v9.1 LTS   9.1.0.4
    
    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

    IT29695

  • Reported component name

    WEBSPHERE MQ 7.

  • Reported component ID

    5724H7240

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-07-11

  • Closed date

    2019-08-19

  • Last modified date

    2019-08-27

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

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

    PH15818

Fix information

  • Fixed component name

    WEBSPHERE MQ 7.

  • Fixed component ID

    5724H7240

Applicable component levels

  • R750 PSY

       UP

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5"}]

Document Information

Modified date:
26 August 2021