|
Problem(Abstract) |
You experience a problem with IBM® Websphere® Application
Server timestamps, as well as application log4j timestamps being written
in GMT time and not local time |
|
|
|
Cause |
WebSphere Application Server variable
ras_time_local and USS® variable TZ were missing |
|
|
Resolving the
problem |
You can resolve this problem by adding the variables
below:
- Set ras_time_local=1 variable in the Administrative console
under Manage WebSphere Variables at the server level (they will appear in
was.env file). The correct timestamp will be shown in WebSphere
Application Server errorlogs and traces sent to SYSPRINT or TRACEFIL
DD.
- In the administrative console under Environment > Manager WebSphere
variables Create the variable TZ and set it to your timezone (for example,
EST5EDT). The log4j api will pick up this variable from the jvm during
application server startup.
Note: Restart the Application Server to pick up these
changes.
|
|
|
|
|
|
|