IBM Support

PH05071: JVM hang when calling GarbageCollectorMXBean.getLastGcInfo for usageMetering-1.0

Fixes are available

18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the usageMetering-1.0 feature is enabled and configured
    to report metrics to the IBM Cloud Private metering service,
    a JVM hang may intermittently occur when usage metering is
    collecting the metric "Java Memory After Garbage
    Collection". The hang occurs when the usage metering feature
    calls
    com.ibm.lang.management.GarbageCollectorMXBean.getLastGcInfo
    to obtain the metric.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty- Product Insights            *
    ****************************************************************
    * PROBLEM DESCRIPTION: JVM hang when calling                   *
    *                      GarbageCollectorMXBean.getLastGcInfo    *
    *                      for usageMetering-1.0                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the usageMetering-1.0 feature is enabled and configured to
    report metrics to the IBM Cloud Private metering service, a JVM
    hang may intermittently occur when usage metering is collecting
    the metric "Java Memory After Garbage Collection". The hang
    occurs when the usage metering feature calls
    com.ibm.lang.management.GarbageCollectorMXBean.getLastGcInfo to
    obtain the metric.
    

Problem conclusion

  • Collection of the "Java Memory After Garbage Collection" metric
    has been disabled for JVMs that do not reliably support
    collection of the metric.
    
    The fix for this APAR is currently targeted for inclusion in fix
    packs 8.5.5.15 and 9.0.0.11 for WebSphere Application Server and
    18.0.0.4 for WebSphere Application Server Liberty.  Please refer
    to the Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH05071

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-11-08

  • Closed date

    2018-11-19

  • Last modified date

    2018-11-19

  • 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

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

  • RCD0 PSY

       UP

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0"}]

Document Information

Modified date:
08 September 2021