IBM Support

PI28937: JAVA.UTIL.LOGGING.LOGGER OBJECTS DO NOT INHERIT LOGGING LEVEL FROM PARENT LOGGER OBJECTS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In WebSphere Application Server V8.0.0.5 and above, when an
    application creates multiple java.util.logging.Logger objects,
    where one Logger is the child of another Logger, the child
    Logger does not inherit the logging level from its parent.
    
    For example, if an application creates Loggers like this:
    
    final Logger parent = Logger.getLogger("com.mycompany");
    parent.setLevel(Level.INFO);
    
    final Logger child =
    Logger.getLogger("com.mycompany.mypackage");
    child.setLevel(Level.ALL);
    
    final Logger grandChild =
    Logger.getLogger("com.mycompany.mypackage.MyClass");
    grandChild.setLevel(null);
    
    System.out.println("Grandchild Level: " +
    grandChild.getLevel());
    
    The getLevel() method for the grandChild logger will return
    null, rather than the level inherited from its parent or
    grandparent.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Logger does not inherit the logger      *
    *                      level from its immediate parent         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When setting up a hierarchy of Loggers, the defined log level
    of the parent is ignored when the log level of the child is
    explicitly set to 'null.' This results in messages being
    skipped.
    

Problem conclusion

  • If a Logger's level is set to null, then its effective level
    is inherited from its parent which may in turn obtain it
    recursively from its parent, and so on up the tree.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.11 and 8.5.5.6.  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

    PI28937

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-11-03

  • Closed date

    2015-01-27

  • Last modified date

    2015-01-27

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

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

Document Information

Modified date:
28 April 2022