PQ70454: WEBSPHERE ERROR MESSAGES PRINTED TO STANDARD ERROR (STDERR) DO NOT HAVE TIMESTAMPS

APAR status
Closed as fixed if next.

Error description
Any errors or messages printed to stderr by WebSphere do not
have timestamps.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of the    *
*                 information in stderr and stdout.            *
****************************************************************
* PROBLEM DESCRIPTION: Information written to standard error   *
*                      or standard out logs does not contain   *
*                      a timestamp.                            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Java code can write to two JVM-supplied output streams,
System.out and System.err.  Information written to System.err
ends up in the stderr log in V4.  Information written to
System.out ends up in the stdout log in V4. (This changes
slightly with the "wrapping log files" function introduced in
4.0.4, but not substantially)
.
If WebSphere code or user code writes to either of these streams
(by using System.out.println()) the data is not automatically
"decorated" with a timestamp or any other information. The
behavior experienced is dictated by the java.io.PrintStream
class. System.out and System.err are instances of that class.
This does not prevent the user from adding a timestamp to the
data that is written to the stream. In fact WebSphere service
messages that show up in the stdout log do exactly that.
When the printStackTrace() method is called on a Throwable, the
default behavior is to print the stack trace to System.err.
The implementation, which is provided by the Throwable class of
the JDK  does not prepend a timestamp to the stack trace
although that would be nice. The implementation is provided by
the JDK and not directly overrideable by WebSphere AppServer.
.
In WebSphere V5 we allow the customer to specify whether or not
they want all data written to System.out and System.err to be
formatted like WebSphere service messages (which would include
a timestamp).  However, this is extra value added in V5. What
the customer is seeing in V4 is standard, expected behavior.
Problem conclusion Temporary fix Comments
APAR information
APAR number PQ70454
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED FIN
PE NoPE
HIPER NoHIPER
Submitted date 2003-01-30
Closed date 2003-02-07
Last modified date 2003-02-07

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels
R400 PSN    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ70454
IBM Group: Software Group
Modified date: Feb 7, 2003