IBM Support

IT20662: amqrmppa process terminates due to SIGSEGV in lpiSPICheckPrivileged function

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • IBM MQ monitoring tool fails to connect to a queue manager with
    2009  - MQRC_CONNECTION_BROKEN.
    
    There is also an FDC being cut against amqrmppa process as
    follows:
    
    Probe Id          :- XC130003
    Application Name  :- MQM
    Component         :- xehExceptionHandler
    Program Name      :- amqrmppa
    Major Errorcode   :- STOP
    Minor Errorcode   :- OK
    Probe Type        :- HALT6109
    Probe Severity    :- 1
    Probe Description :- AMQ6109: An internal WebSphere MQ error has
    occurred.
    Arith1            :- 11 (0xb)
    Comment1          :- SIGSEGV: address not mapped(0)
    
    MQM Function Stack
    ccxResponder
    rrxResponder
    ccxReceiveThreadFn
    cciProcessOne
    cciProcessUserData
    cciProcessAsyncRcv
    rriServerAsyncRcv
    rriMQIServerReceive
    rriMQIServerCall
    rriCheckUserBlocked
    rsxIsUserAllowed
    lpiSPICheckPrivileged
    xcsFFST
    

Local fix

  • The FFST can be avoided by switching off MQ trace.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of of WebSphere MQ 7.5 on Solaris
    x86-64 who have configured queue manager access controls using
    Channel Authentication (CHLAUTH) rules of type BLOCKUSER and who
    enable MQ trace using the strmqtrc command.
    
    
    Platforms affected:
    Solaris x86-64
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The problem occurred when MQ trace was started on the queue
    manager and a client application was connected.  To trace the
    connection the queue manager attempted to print a string whose
    value was a 0 (null) pointer which resulted in a SIGSEGV and the
    queue manager's amqrmppa process terminating.  The client
    connection attempt was unsuccessful.
    

Problem conclusion

  • The MQ queue manager logic has been corrected to prevent a null
    pointer access in this scenario.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.9
    
    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

    IT20662

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7241

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-18

  • Closed date

    2017-05-31

  • Last modified date

    2017-05-31

  • 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 BASE MULTIP

  • Fixed component ID

    5724H7241

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
31 May 2017