IBM Support

IT15004: FDC with probe ID HL086204 generated in mqlReclaimExtents but the queue manager does not stop as expected

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A Failure Data Capture (FDC) file with Probe Id HL086204 is
    generated:
    .
      Probe Id          :- HL086204
      Component         :- mqlReclaimExtents
      Process Name      :- D:\MQSeries\bin\amqzmuc0.exe
      Major Errorcode   :- xecF_E_UNEXPECTED_RC
      Minor Errorcode   :- STOP_ALL
      Probe Type        :- MSGAMQ6118
      Probe Description :- AMQ6118: An internal WebSphere MQ
                           error has occurred  (40406110)
      Arith1            :- 1077960976 40406110
      ------------------------------------------------------
      MQM Function Stack
      zmuThreadMain
      zmuLogIOTask
      mqlpgasn
      mqlReclaimExtents
      xcsFFST
    .
    The expectation is that the queue manager would stop when
    this is generated but it does not.
    

Local fix

  • Manually restart the queue manager using a graceful shutdown if
    an FDC with probe ID HL086204 is observed and the queue manager
    continues to run after the FDC is generated.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    IBM MQ Server applications
    
    
    Platforms affected:
    Linux on x86-64, Linux on x86, Solaris x86-64, Solaris SPARC,
    AIX, HP-UX Itanium, HP-UX PA-RISC, HP-UX OpenVMS, IBM iSeries,
    Linux on Power, Linux on S390, Linux on zSeries, Windows,
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The FDC indicates IBM MQ encountered an unexpected state when
    working with the Transaction Logs whilst reclaiming log extents.
     In this state the internal counters are not correctly aligned
    to the current state of logger extents so further undefined
    problems may occur, and so the queue manager should have stopped
    such that the counters could be re-aligned to their correct
    values on restart.
    
    Even though the FDC indicated a STOP condition, the queue
    manager incorrectly continued to run.
    

Problem conclusion

  • In addition to ensuring the queue manager stops as intended in
    this scenario, IBM MQ has been updated with additional
    diagnostic capability that improves the detection of the
    discrepancies that lead up to the FDC.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.1       7.1.0.9
    v7.5       7.5.0.8
    v8.0       8.0.0.7
    
    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

    IT15004

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-04-28

  • Closed date

    2017-06-06

  • Last modified date

    2017-07-06

  • 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 WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R710 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1"}]

Document Information

Modified date:
09 March 2021