IBM Support

PI72776: WHEN WLP_ZOS_PROCEDUREIS SET THE FOREGROUND JVM USES THE FULL SET OF JVM OPTIONS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The standard behavior of the "server" script is always to
    start
    a background process which creates a foreground JVM for
    monitori
    ng the server's startup. This foreground JVM should not
    consume
    the JVM specs of the background. But contrary to distributed
    on zOS the foreground JVM copies all the JVM settings of the
    background JVM when running without WLP_ZOS_PROCEDURE.
    

Local fix

  • Don't set WLP_ZOS_PROCEDURE
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty for z/OS                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: WHEN WLP_ZOS_PROCEDURE IS SET, THE      *
    *                      FOREGROUND JVM USES THE FULL SET OF JVM *
    *                      OPTIONS                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The standard behavior of the "server" script is always to start
    a background process that will eventually become the running
    application server and to then, after the background process is
    created, create a JVM in the foreground process for the sole
    purpose of connecting to and monitoring the background process
    for proper completion, so that the server script can report
    status back to the invoker of the shell script.
    
    The background process launches a JVM that will contain the
    application server, and this JVM consumes all of the JVM options
    specified by the end user in the various supported jvm.options
    files in the server's configuration directory.
    
    The foreground process JVM is only a transient JVM for
    monitoring the startup of the server and is not designed to
    consume all of those JVM options. So, for example, the end user
    might have specified a 4 GB heap for their application server,
    but we certainly don't need a 4 GB heap in the foreground JVM.
    The foreground JVM is meant to be started with a bare minimum
    set of JVM options.
    

Problem conclusion

  • The JVM options were stored prior to being overriden with those
    used for the server start, those stored options were never
    restored after the server launch had been invoked.  This has
    been corrected in the server script.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 17.0.0.1.  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

    PI72776

  • Reported component name

    LIBERTY PROF -

  • Reported component ID

    5655W6514

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-11-24

  • Closed date

    2017-01-30

  • Last modified date

    2017-01-30

  • 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 PROF -

  • Fixed component ID

    5655W6514

Applicable component levels

  • RCD0 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"CD0","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
17 June 2020