Fixes are available
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as new function.
Error description
Serviceability enhancement.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: Messages within the native_stderr * * and native_stdout log files lack * * timestamps. * **************************************************************** * RECOMMENDATION: * **************************************************************** The application server can now prepend a timestamp and thread identifier to all server debug messages output to the native_stdout and native_stderr log files. The time stamp and thread identifier enhance serviceability by enabling the correlatation between the behaviors of primordial server mechanisms to the behaviors of other server mechanisms indicated in the SystemOut and SystemErr log fles. Here is a snippet of debug messages emitted by the server when APAR PM65557 is enabled, and the server is configured with JVM generic argument -Dws.ext.debug=true (a system property in the server JVM process.) This configuration will cause the server to emit debug messages during its bootstrapping sequence. [6/18/12 16:24:31:453 CDT] 00000000 ws.ext.mains.args[0]=-nosplash [6/18/12 16:24:31:453 CDT] 00000000 ws.ext.mains.args[1]=-application [6/18/12 16:24:31:453 CDT] 00000000 ws.ext.mains.args[2]=com.ibm.ws.bootstrap.WSLauncher [6/18/12 16:24:31:453 CDT] 00000000 ws.ext.mains.args[3]=com.ibm.ws.runtime.WsServer If you want messages within the native_stdout and native_stderr log files to contain time and thread information, add the following JVM generic argument to the server settings. Notice that behavior is disabled by default. Name -Dcom.ibm.websphere.native.logging.timestamp Value Set to true or false to enable time stamps and thread information in messages written to native_stdout.log and native_stderr.log. Default False Messages written by the JVM to the System.out and System.err print streams are logged, respectively, to the native_stdout.log and native_stderr.log files. JVM messages will not have time and thread information when APAR PM65557 is enabled.
Problem conclusion
Apply APAR PM65557 to enhance serviceablilty of the application server by adding the capability to prepend time and thread information to messages written to the native_stderr and native_stdout log files. The fix for this APAR is currently targeted for inclusion in fix packs 8.5.0.1 amd 8.0.0.4. 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
PM65557
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-05-25
Closed date
2012-06-25
Last modified date
2012-06-25
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
Document Information
Modified date:
28 October 2021