IBM Support

PI39293: AdminCenter line graphs plots can get out of sync with the summa ry field values.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the system hosting the AdminCenter is under heavy load,
    the line plots in the graphs, can get out of sync with the
    Summary values e.g the JVM Heap size graph won't plot the
    same value as is displayed in the Used field.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile - Liberty            *
    *                  Administrative Center                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: AdminCenter line graphs plots can get   *
    *                      out of sync with the summary field      *
    *                      values.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the system hosting the AdminCenter is under heavy load, the
    line plots in the graphs, can get out of sync with the Summary
    values. For example, the JVM Heap size graph won't plot the same
    value as is displayed in the Used field.
    

Problem conclusion

  • When we scroll the AdminCenter line graphs, we always update the
    X Axis for the timestamps of the datapoints. Originally, this
    was done by taking the timestamp of the first datapoint, and
    calculating the end timestamp, based on the maximum number of
    datapoints that can be displayed in the graph and the refresh
    rate of the graph. This meant that if for any reason the
    timestamp of the last datapoint didn't match the predicted
    value, the line graph wouldn't plot correctly.
    The fix now only calculates the end timestamp if we don't have a
    full set of datapoints, and if we do have the full number of
    datapoints defined, it uses the actual timestamp of the last
    datapoint.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.6.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Refreshing the browser screen will re-initialise the graphs and
    resync the summary and plot lines.
    

Comments

APAR Information

  • APAR number

    PI39293

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-04-17

  • Closed date

    2015-05-06

  • Last modified date

    2015-05-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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022