IBM Support

IT29854: IBM MQ Console chart widgets stop updating

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

  • A user adds some chart widgets for different queue managers to
    their IBM MQ Console dashboard. After running for a period of
    time, the chart widgets for one or more of the queue managers
    stop being updated, even though the IBM MQ Console shows that
    the queue managers are running.
    

Local fix

  • Ensure that all users have logged out of the IBM MQ Console.
      - Log into the IBM MQ Appliance.
      - From the mqcli, enter the command:
          mqwebui stop
        This will stop the IBM MQ web server hosting the IBM MQ
    Console
      - Restart the IBM MQ web server, by entering the command:
          mqwebui start
        from the mqcli.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the IBM MQ Console who have a
    dashboard containing one or more chart widgets associated with
    different queue managers.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Every chart widget that is added to the IBM MQ Console dashboard
    has an internal "com.ibm.mq.ui.collector.ResourceTopic" object
    associated with it. The ResourceTopic object contains
    information about the resource being monitored, such as:
    
    - The name of the queue manager.
    - The topic string for the monitoring topic on the queue manager
    that contains the data.
    - The name of the non-durable subscription on the topic string
    that collects the monitoring data.
    - The JMS Connection and Session used to create the
    subscription.
    - Whether the ResourceTopic is collecting data or not.
    - The last time that data was collected.
    
    The subscription associated with the ResourceTopic is created
    when the chart widget is first added to the dashboard, and
    remains in place until the IBM MQ web server hosting the IBM MQ
    Console is stopped.
    
    Periodically, the IBM MQ Console will perform a "refresh
    operation". As part of this operation, it will look at each
    ResourceTopic object in turn to see if they are collecting any
    data. If it finds a ResourceTopic that is not collecting any
    data, then it will attempt to restart it. This involves
    recreating a new JMS Connection, and non-durable subscription if
    necessary.
    
    
    If a dashboard contained multiple chart widgets for different
    queue managers, and one or more of the queue managers that was
    being monitored became unavailable for some reason, then the
    ResourceTopics associated with the chart widgets for those queue
    managers would be put in a "not collecting" state. The IBM MQ
    Console would then attempt to restart them during the next
    "refresh operation". However, if the attempt to restart a
    ResourceTopic for a chart widget failed (because a JMS
    Connection could not be created to the queue manager, for
    example), then the IBM MQ Console would not attempt to restart
    any of the other ResourceTopics that were also in the "not
    collecting" state.
    
    As a result, these chart widgets associated with this
    ResourceTopic objects would not be updated.
    

Problem conclusion

  • The IBM MQ Console has been updated to try and restart all of
    the ResourceTopics that are in a "not collecting" state during
    each "refresh operation".  This means that chart widgets
    associated with ResourceTopics for queue managers that are
    currently running will now be updated as part of each "refresh
    operation".
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 CD    9.1.4
    v9.1 LTS   9.1.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

    IT29854

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-07-26

  • Closed date

    2019-09-27

  • Last modified date

    2019-09-27

  • 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

    5724H7271

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":"910","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 September 2019