IBM Support

PH09657: Usage Metering discards metrics on HTTP 500 response from metering service

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The usage metering feature collects usage metrics every 15
    minutes and sends them to the IBM Cloud Private metering
    service.  When the metering service is taken down or
    re-started, the reporting WebSphere application server may
    receive an HTTP 500 response code, and handles the response
    by discarding the usage metrics.  For that 15 minute
    interval, the usage metrics displayed on the metering
    dashboard will be missing / inaccurate.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty- Usage Metering              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Usage Metering discards metrics on      *
    *                      HTTP                                    *
    *                      500 response from metering service      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The usage metering feature collects usage metrics every 15
    minutes and sends them to the IBM Cloud Private metering
    service.  When the metering service is taken down or re-
    started,
    the reporting WebSphere application server may receive an
    HTTP
    500 response code, and handles the response by discarding
    the
    usage metrics.  For that 15 minute interval, the usage
    metrics
    displayed on the metering dashboard will be missing /
    inaccurate.
    

Problem conclusion

  • The usage metering feature in WebSphere application server
    has
    been updated to properly handle the HTTP 500 response by
    caching
    the usage metrics and sending the information later when the
    metering service is reachable. The usage metrics will no
    longer
    be lost, and will display properly and accurately on the IBM
    Cloud Private metering dashboard.
    
    The fix for this APAR is currently targeted for inclusion in
    fix
    pack 19.0.0.3 for WebSphere Application Server Liberty and
    9.0.5.0 and 8.5.5.16 for WebSphere Application Server.
    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

    PH09657

  • 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

    2019-03-12

  • Closed date

    2019-03-21

  • Last modified date

    2019-04-04

  • 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

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

Document Information

Modified date:
17 June 2020