PK73526: LOGGING CONFIGURATION SETTINGS DEFINED IN PROPERTIES FILE DOES NOT TAKE EFFECT.

Fixes are available

APAR status

Closed as program error.

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

Temporary fix

Comments

APAR Information

APAR number
PK73526
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-09
Closed date
2008-11-11
Last modified date
2008-11-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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK73526: LOGGING CONFIGURATION SETTINGS DEFINED IN PROPERTIES FILE DOES NOT TAKE EFFECT.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?