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

8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

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