IBM Support

IT33261: The amqrmppa process terminates with memory exception in rppAdjustPool or rppLockPool

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

  • The amqrmppa process terminates with a SIGSEGV when acquiring a
    mutex from
    rppLockPool or rppAdjustPool.
    
    amqrmppa    22563   30984 ZS402099 zstAsyncConsume
    MQRC_SYNCPOINT_NOT_AVAILABLE
    amqrmppa    22563   30917 XC130003 xehExceptionHandl     STOP
    amqrmppa    22563   30917 RM454101 rppAdjustPool            STOP
    
    The following failure data capture (FDC) records can be
    observed:
    
    Probe Id          :- XC130003
    Application Name  :- MQM
    Component         :- xehExceptionHandler
    Program Name      :- amqrmppa
    Thread            :- 501    RemoteResponder
    Major Errorcode   :- STOP
    Probe Type        :- HALT6109
    Arith1            :- 11 (0xb)
    Comment1          :- SIGSEGV: address not mapped((nil))
    
    
    O/S Call Stack and MQM Function Stack  with rppLockPool on top
    of stack.
    
    /opt/mqm/lib64/libmqmcs_r.so(+0x103ff8)[0x7fb2f1fb9ff8]
    /opt/mqm/lib64/libmqmcs_r.so(+0x1268ba)[0x7fb2f1fdc8ba]
    /opt/mqm/lib64/libmqmcs_r.so(+0x125b18)[0x7fb2f1fdbb18]
    /opt/mqm/lib64/libmqmcs_r.so(xcsFFSTFn+0x203f)[0x7fb2f1fde97f]
    /opt/mqm/lib64/libmqmcs_r.so(xehExceptionHandler+0x6c9)[0x7fb2f1
    fd1239]
    /lib64/libpthread.so.0(+0xf970)[0x7fb2f16ef970]
    /opt/mqm/lib64/libmqmcs_r.so(xcsRequestMutexSemFn+0x95)[0x7fb2f2
    000dc5]
    /opt/mqm/lib64/libmqmr_r.so(rppLockPool+0xa7)[0x7fb2f2e5d1e7]
    /opt/mqm/lib64/libmqmr_r.so(rppFindPID+0xab)[0x7fb2f2e5e97b]
    /opt/mqm/lib64/libmqmr_r.so(rppAdjustPool+0x1b8)[0x7fb2f2e5fe78]
    /opt/mqm/lib64/libmqmr_r.so(cciResponderThread+0x2cf)[0x7fb2f2c8
    ea9f]
    /opt/mqm/lib64/libmqmcs_r.so(+0x19585e)[0x7fb2f204b85e]
    /lib64/libpthread.so.0(+0x7e91)[0x7fb2f16e7e91]
    /lib64/libc.so.6(clone+0x6d)[0x7fb2f120ecbd]
    
    MQM Function Stack
    rppAdjustPool
    rppFindPID
    rppLockPool
    xcsFFST
    
    O/S Call Stack and MQM Function Stack  with rppAdjustPool on top
    of stack:
    
    /opt/mqm/lib64/libmqmcs_r.so(xcsPrintStackForCurrentThread+0x3e)
    [0x7f17912c6e3e]
    /opt/mqm/lib64/libmqmcs_r.so(+0x11596a)[0x7f17912e196a]
    /opt/mqm/lib64/libmqmcs_r.so(PrepareDumpAreas+0xc07)[0x7f17912e0
    7d7]
    /opt/mqm/lib64/libmqmcs_r.so(xcsFFSTFn+0xb7b)[0x7f17912e2a2b]
    /opt/mqm/lib64/libmqmcs_r.so(xehExceptionHandler+0x6c1)[0x7f1791
    2da051]
    /usr/lib64/libpthread.so.0(+0xf5d0)[0x7f1790a1d5d0]
    /opt/mqm/lib64/libmqmcs_r.so(xcsRequestMutexSemFn+0x95)[0x7f1791
    2fce65]
    /opt/mqm/lib64/libmqmr_r.so(rppAdjustPool+0x376)[0x7f179205a766]
    /opt/mqm/lib64/libmqmr_r.so(rriAsyncConvControl+0x94f)[0x7f17920
    29bff]
    /opt/mqm/lib64/libmqmr_r.so(cciEndConv+0x22c)[0x7f1791e793ec]
    /opt/mqm/lib64/libmqmr_r.so(ccxReceiveThreadCleanup+0x112)[0x7f1
    791e7d542]
    /opt/mqm/lib64/libmqmr_r.so(ccxReceiveThreadFn+0xda)[0x7f1791e7d
    9aa]
    /opt/mqm/lib64/libmqmr_r.so(rrxResponder+0x6ef)[0x7f179203fa8f]
    /opt/mqm/lib64/libmqmr_r.so(ccxResponder+0x274)[0x7f1791e8a2b4]
    /opt/mqm/lib64/libmqmr_r.so(cciResponderThread+0x8b)[0x7f1791e8a
    4ab]
    /opt/mqm/lib64/libmqmcs_r.so(+0x16f05e)[0x7f179133b05e]
    /usr/lib64/libpthread.so.0(+0x7dd5)[0x7f1790a15dd5]
    /usr/lib64/libc.so.6(clone+0x6d)[0x7f179053b02d]
    
    MQM Function Stack
    ccxResponder
    rrxResponder
    ccxReceiveThreadFn
    ccxReceiveThreadCleanup
    cciEndConv
    rriAsyncConvControl
    rppAdjustPool
    xcsFFST
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using MQ client applications with async consume feature in
    XA environment with an external transaction manager.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    MQ did not handle an XA error condition 2072 and this caused
    memory exception (SIGSEGV) in amqrmppa process.
    

Problem conclusion

  • MQ code has been modified to handle the XA error condition to
    resolve the problem.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 LTS   9.0.0.12
    v9.1 LTS   9.1.0.8
    v9.2 LTS   9.2.0.2
    v9.x CD    9.2.2
    
    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

    IT33261

  • Reported component name

    MQ APPLIANCE M2

  • Reported component ID

    5737H4700

  • Reported release

    915

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-06-18

  • Closed date

    2021-03-23

  • Last modified date

    2021-07-01

  • 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 APPLIANCE M2

  • Fixed component ID

    5737H4700

Applicable component levels

[{"Type":"MASTER","Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
02 July 2021