IBM Support

IT23673: Internal errors reported after MQ health check thread detects a problem with file system

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

  • FDC reports a memory exception (SIGSEGV) after the file lock
    thread for
    a Multi-instance queue manager becomes unresponsive.
    
    FDCs report:
    
    Probe Id :- XC130003
    Component :- xehExceptionHandler
    Program Name :- amqzxma0
    Thread :- 12 FileLockMonitor
    Major Errorcode :- STOP
    Probe Type :- HALT6109
    Probe Description :- AMQ6109: An internal WebSphere MQ error
    has occurred.
    Arith1 :- 11 (0xb)
    Comment1 :- SIGSEGV: address not mapped(0x8)
    
    MQM Function Stack
    zxcFileLockMonitorThread
    zxcInquireAndUpdateStatus
    xlsPostEvent
    xcsFFST
    
    Probe Id :- XC333101
    Component :- xlsPostEvent
    Major Errorcode :- STOP
    
    Trace shows:
    
    ---{ xcsFFST
    ErrorCode :- 40406109 Numeric Insert1 :- 0000000b (11) Numeric
    Insert2 :- 00000000 (0)
    String Insert :- 'SIGSEGV: address not mapped(0x8)'
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of multi-instance queue managers may be affected by this
    issue.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When using multi-instance queue managers, MQ uses a file lock
    monitor to check the health of the file system. If the queue
    manager is no longer responsive, if for example it loses a
    connection to a shared file system, then the queue manager is
    supposed to end.
    
    During this sequence of events an unexpected additional error
    condition occurred due to a queue manager resource being
    unavailable from the lock monitor thread. This unexpected
    additional error condition was reported by the Failure Data
    Capture (FDC) record above.
    

Problem conclusion

  • The IBM MQ code was corrected so that the necessary queue
    manager resource was available to the file lock monitor thread.
    
    ---------------------------------------------------------------
    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

    IT23673

  • 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

    2018-01-09

  • Closed date

    2018-02-01

  • Last modified date

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

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