IBM Support

PI73782: Customization of log Filenames and paths affected by WAS variable SERVER_LOG_ROOT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer wants to customize log output path and filenames
    for
    dynamic clusters. Configuring WAS ND 8.5 on Linux RHEL 7.
    Trying to configure the dynamic cluster template for JVM log
    files to customize path/structure of where the log files for
    each JVM will be wriiten to and filename.  Customer created
    variables to put in the path to allow it not to interfere
    with
    other JVMs location.  Each time a save and synch is done, it
    throws the WAS variable ${SERVER_LOG_ROOT} in the beginning
    of
    the variable path. Needed for developers, to give them
    limited
    access to the logs directories,  to store them all in one
    place
    or one main directory, and separate them out there by
    different
    names. In dynamic cluster template, it allows to change the
    location of the System out and System Err. Can put custom
    variable names in there to separate out the logging from
    other
    vertical cluster members.  When saved, System Err handles it
    fine and keeps it.  The System Out File Name continues to
    force
    in a ${SERVER_LOG_ROOT} variable in front of the custom
    location.
    

Local fix

  • use "" for SERVER_LOG_ROOT - unconfirmed
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server WAS ND edition- Virtual              *
    *                  Enterprise/IM Component                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Log Filenames and paths affected by WAS *
    *                      variable SERVER_LOG_ROOT                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Dynamic clusters rely upon a server template that propagates out
    to each cluster member. However, when log files are written
    collisions must be avoided so that each server can write to its
    own log file. If you attempted to set the log files for a
    dynamic cluster member to an absolute path, the page would
    detect this and append ${SERVER_LOG_ROOT} to the start of your
    path. This ensured collisions were avoided, but made it
    impossible to redirect the log files to the custom locations.
    

Problem conclusion

  • After this fix, if you specify an absolute path, which does not
    contain either the ${SERVER_LOG_ROOT} or the ${WAS_SERVER_NAME}
    variable it will add ${WAS_SERVER_NAME} to the start of
    SystemOut.log or SystemErr.log. This will prevent the collisions
    from each member of the dynamic cluster writing file. If you use
    either ${SERVER_LOG_ROOT} or put the server name variable
    ${WAS_SERVER_NAME} in the path given it will assume you have
    properly accounted for collisions and do nothing.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.11.  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

    PI73782

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-12-14

  • Closed date

    2017-01-11

  • Last modified date

    2017-01-11

  • 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

  • R850 PSY

       UP

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

Document Information

Modified date:
19 October 2021