IBM Support

PH22062: LOG THE DEFAULT JVM MAXIMUM HEAP SIZE COMPUTATION

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

  • WebSphere Application Server does not log, at startup, the
    default maximum heap size of the server JVM when starting
    a server process.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: The automatically-calculated maximum    *
    *                      heap                                    *
    *                      size of the server JVM is not logged    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a user does not specify a maximum heap size or a -Xmx
    argument for the a WAS 9 server JVM, the server launcher
    calculates and uses a default value (25% of the system's
    physical RAM, up to 4GB). This calculation and its result are
    not logged without enabling trace of the server start process,
    so that data is unavailable in a server's log set without taking
    additional steps (such as enabling trace and restarting the
    server, or forcing javacores). This can prolong the diagnostic
    process for a case involving memory analysis, and it can be
    confusing for users who are not aware of how their maximum heap
    size is set, and to what value.
    

Problem conclusion

  • Message ADML0069I was added to startServer.log in instances
    where the maximum heap size is unspecified. The message states
    that the JVM maximum heap size was automatically calculated and
    notes the calculated value and corresponding -Xmx argument.
    
    The fix for this APAR is targeted for inclusion in fix pack
    9.0.5.15. For more information, see 'Recommended Updates for
    WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH22062

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-02-12

  • Closed date

    2023-03-22

  • Last modified date

    2023-03-22

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

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

Document Information

Modified date:
23 March 2023