PK73526; 6.1.0.21: logging configuration settings defined in properties file

Download Description

PK73526 resolves the following problem:

ERROR DESCRIPTION:
Logging configuration settings defined in properties file does not take effect.

It appears that Application Server sets the Level of the logger based onthe TraceSpec upon construction of the logger. This makes it such that the Level cannot be defined by a properties
file.

The customer is looking for a way to have this behavior be configurable. In other words, while they would like the default logging behavior to remain, they would like the ability to set some variable such that it allows the logger to be configured via a properties file.

LOCAL FIX:
No work around available.

PROBLEM SUMMARY:

USERS AFFECTED:
WebSphere Application Server V6.1 and V7.0 users who want to modify the java.util.logging configuration in the server via a properties file. This is not a recommended practice.

PROBLEM DESCRIPTION:
Logger Levels are not modified properly by Properties files

RECOMMENDATION:
Recommend not using properties files on a server for logging changes as they impact
all who are on the server.

Due to full initialization of loggers during logger initialization, the level changes introduced by properties
files were not propagated

PROBLEM CONCLUSION:
By using the environment variable:
java.util.logging.configureByLoggingPropertiesFile=true the initialization of loggers is cut short so that the level is not set by the TraceSpec. It should be noted that, if the Administrative Console or a wsadmin script to update the traceSpec dynamically is run, then all loggers will be initialized per this mechanism and the properties file levels will no longer be in effect.

The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.23 and 7.0.0.3.

Please refer to the Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980