IBM Support

IT44106: High CPU usage in MQ appliance when or after using dspmqerr command

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

  • When using the dspmqerr command to review the queue manager logs
    or other support, it has been
    observed that sometimes the session continues running in the
    background, leading to high CPU usage.
    
    This issue can be identified by observing a higher CPU usage
    than usual in the output of the status command, as shown below:
    
    mqa(mqcli)# status
    Memory:                                  187.8GB total, 20683MB
    used [11%]
    CPU:                                     54%
    CPU load:                                7.32, 6.95, 6.75
    ...
    
    Upon reviewing the ps output captured by runmqras report, it was
    discovered one or more "less" processes, internally used by the
    dspmqerr command, were consuming high CPU.
    
    Example:
    
      18939       1    1 R   6732  0.0 97.0   Apr 11 77-15:04:43
       mqsystem mqm   mqsystem mqm      less
    /var/mqm/vols/QM1/qmgr/QM1/errors/AMQERR01.LOG
    364614       1    1 R   6732  0.0 98.5   May 17 42-18:32:48
    mqsystem mqm   mqsystem mqm      less
    /var/mqm/vols/QM2/qmgr/QM2/errors/AMQERR01.LOG
    

Local fix

  • Contact IBM Support to provide instructions on how to remove
    the orphaned processes.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using dspmqerr command to view logs(e.g. queue manager
    logs) in MQ appliance
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    This problem was due to orphaned processes internally used by
    the dspmqerr command.
    

Problem conclusion

  • MQ code has been modified to end the orphaned processes to
    resolve the high CPU issue.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.3 LTS   9.3.0.20
    v9.4 LTS   9.4.0.0
    
    The latest available maintenance can be obtained from
    'IBM MQ Recommended Fixes'
    https://www.ibm.com/support/pages/recommended-fixes-ibm-mq
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'IBM MQ
    Planned Maintenance Release Dates'
    https://ibm.biz/mqplannedmaintenance
    
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT44106

  • Reported component name

    MQ APPL M2002

  • Reported component ID

    5737H4701

  • Reported release

    925

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-07-05

  • Closed date

    2024-02-06

  • Last modified date

    2024-05-14

  • 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 APPL M2002

  • Fixed component ID

    5737H4701

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"925","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
14 May 2024