IBM Support

IT24336: The status MQCLI control command shows negative memory usage

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 status MQCLI control command shows a negative value for the
    "Memory"
    attribute:
    
    mqa(mqcli)# status MYQM
    QM(MYQM)                            Status(Running)
    CPU:                                     5.83%
    Memory:                                  -34402MB
    Queue manager file system:               112960MB used, 344.6GB
    allocated [32%]
    HA role:                                 Primary
    HA status:                               Normal
    HA control:                              Enabled
    HA preferred location:                   This appliance
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of the status MQCLI control command, REST API interface,
    or Appliance Web UI may be affected by this issue.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    IBM MQ keeps an internal record of how much memory each thread
    has allocated and this value is used to determine the value that
    is exposed via the MQCLI status command, the REST API interface,
    and the Appliance Web UI Queue Manager Status view.  Some IBM MQ
    threads recorded this number as a negative value and so the
    status command showed incorrect information about the memory
    that a queue manager was using.
    

Problem conclusion

  • The IBM MQ code has been modified to ignore negative values when
    calculating the total memory usage.  A programming error has
    also been corrected where the structure used to record the
    memory usage for an IBM MQ thread was being incorrectly reused
    across thread instances without first being cleared.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.12
    v9.1 CD    9.1.1
    v9.1 LTS   9.1.0.1
    
    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

    IT24336

  • Reported component name

    IBM MQ APPL M20

  • Reported component ID

    5725S1400

  • Reported release

    903

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-03-09

  • Closed date

    2018-07-09

  • Last modified date

    2019-04-24

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

  • Fixed component ID

    5725S1400

Applicable component levels

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

Document Information

Modified date:
24 April 2019