PK54209: ENHANCED CUSTOM LOGGING FUNCTIONALITY FOR USING SYSTEMOUT STREAM

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• A switch is being added in order to allow custom logging
  functionality to write directly to the SystemOut stream without
  including excess information (timestamp, threadID, etc).
  
  This is due in part to the fact that IBM WebSphere Application
  Server controls the formatting of the SystemOut stream to a
  larger extent.  This switch will prevent that from happening.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM WebSphere Application Server version     *
  *                 6.0.2 and 6.1 users who wish to write        *
  *                 directly to the SystemOut.log or             *
  *                 SystemErr.log files.                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: All System.out.println(...)'s are       *
  *                      pre-pended with additional data.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using System.out.println(...) or System.err.println(...)
  the data getting printed is pre-pended with logging text
  such as the date/timestamp, thread ID, logger name, and so on.
  
  There are times when it is necessary to print directly to
  these output files with no pre-pended data.
  

Problem conclusion

• In order to disable the log formatting, you must set this
  system property to "true":
  com.ibm.ejs.ras.writeSystemStreamsDirectlyToFile
  
  You can set this property in the Administrative Console
  by browsing to Servers -> Application Servers ->
  <server_name> -> Java and Process Management -> Process
  Definition -> Java Virtual Machine.  From this panel, add
  the text following text to the text field labeled,
  "Generic JVM arguments":
   -Dcom.ibm.ejs.ras.writeSystemStreamsDirectlyToFile=true
  
  With this system property set to true, the log formatting
  data (timestamp, thread ID, etc.) will not be printed when
  using System.out.println(...) or System.err.println(...).
  
  This fix is targetted for inclusion in fix packs 6.0.2.25 and
  6.1.0.15.
  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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R60A PSY

     UP

• R60H PSY

     UP

• R60I PSY

     UP

• R60P PSY

     UP

• R60S PSY

     UP

• R60W PSY

     UP

• R60Z PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP