IBM Support

IT23576: runmqchi terminates with memory exception in rriCheckChannels

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 MQ channel initiator process runmqchi terminates
    unexpectedly because of a memory
    exception(SIGSEGV on UNIX/LINUX). The following Failure Data
    Capture (FDC) records might be generated during the failure.
    
      Probe Id          :- XC130003
      Component         :- xehExceptionHandler
      Program Name      :- runmqchi
      Thread            :- 1    ChannelInitiator
      Major Errorcode   :- STOP
      Probe Type        :- HALT6109
      Arith1            :- 11 (0xb)
      Comment1          :- SIGSEGV: address not mapped
    (0x7fbb19334e30)
    
      MQM Function Stack
      riiInitiator
      riiCheckChannels
      xcsFFST
    
      Probe Id          :- RM058101
      Component         :- riiCheckChannels
      Program Name      :- runmqchi
      Thread            :- 1    ChannelInitiator
      Major Errorcode   :- STOP
      Probe Type        :- HALT6109
    
      MQM Function Stack
      riiInitiator
      riiCheckChannels
      xcsFFST
    

Local fix

  • Restart the channel initiator.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using MQ channel initiators
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    This problem occurred because runmqchi process did not correctly
    manage the memory references associated with the channels and
    this caused the process to access an incorrect memory address,
    which resulted in a memory exception.
    

Problem conclusion

  • The MQ channel initiator logic has been corrected to prevent the
    illegal memory access.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.9
    v9.0 CD    9.0.5
    v9.0 LTS   9.0.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

    IT23576

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-12-26

  • Closed date

    2018-01-31

  • Last modified date

    2018-01-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

    IBM MQ BASE MP

  • Fixed component ID

    5724H7251

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
31 January 2018