IBM Support

IT45113: SIGSEGV in reconnectable MQ client application

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • An MQ client application crashes and dumps core (if enabled by
    the system) when attempting to use MQ client reconnection
    functionality.
    
    The following information (or similar) would be seen in the FDC
    file that is written by the MQ code running in the application.
    
    Here is an example from a MQ 9.3 client:
    Probe Id          :- XC130003
    Component         :- xehExceptionHandler
    Thread            :- 23    RemoteReconnect
    Arith1            :- 11 (0xb)
    Comment1          :- SIGSEGV: address not mapped(0xfffffff0)
    
    O/S Call Stack for current thread
    /opt/mqm/lib/libmqe_r.so(+0x3cbfa1)[0x56c2ffa1]
    ...
    MQM Function Stack
    rcnReconnectThread
    rcnDoReconnec
    zutLookupIterate
    rcnRecreateHandle
    rcnUpdateConnReconnectFail
    rcnFreeConnReconnectFailObject
    xcsFreeMemFn
    xcsCheckMem
    xcsFFST
    
    For 9.2 clients, the rcnFreeConnReconnectFailObject will not
    appear in the FFST call stack, but the remaining call stack will
    be similar.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    MQ Reconnectable Client applications using publish subscribe
    messaging running on unreliable networks
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A small window exists where if a client's network connection
    fails again whilst recovering from a network failure, the MQ
    client library attempts to free resources that have not been
    allocated.
    

Problem conclusion

  • Extra checks have been put in place to verify the memory is
    allocated before trying to free it.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.25
    v9.3 LTS   9.3.0.20
    v9.4 LTS   9.4.0.0
    
    The latest available maintenance can be obtained from
    'IBM MQ Recommended Fixes'
    https://www.ibm.com/support/pages/recommended-fixes-ibm-mq
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'IBM MQ
    Planned Maintenance Release Dates'
    https://ibm.biz/mqplannedmaintenance
    
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT45113

  • Reported component name

    MQ BASE V9.3

  • Reported component ID

    5724H7291

  • Reported release

    930

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-12-11

  • Closed date

    2024-03-26

  • Last modified date

    2024-05-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

    MQ BASE V9.3

  • Fixed component ID

    5724H7291

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"930","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
14 May 2024