PH46573: ADD FULL HEADERS TO ERROR-STREAM LOGS

APAR status

• Closed as program error.

Error description

• Currently, the WAS error-stream logs (SystemOut.log and
  native_stderr.log) contain truncated headers that do not contain
  system and process information, making debug efforts more
  complicated when utilizing those logs.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: The headers of SystemErr.log and        *
  *                      native_stderr.log contain incomplete    *
  *                      information                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Since WAS 6.1, SystemErr.log and native_stderr.log have
  contained "limited" headers - rather than the set of details in
  the headers of SystemOut.log and native_stdout.log (including
  server name, process ID, and a variety of environmental
  details), they contain only the time at which the log was
  created. This can be problematic when analyzing log sets from
  large topologies, as the error logs do not contain the process
  ID or name of the associated server, and even in cases in which
  the process ID and name are not in question, finding
  environmental data requires going back to the full headers in
  the other logs.
  

Problem conclusion

• The default header type for the error-stream logs was changed
  from "limited" to "full".
  
  If the previous header behavior is required, create a JVM custom
  property on the server process named
  "com.ibm.websphere.logging.errheading" with value "limited", or
  add "-Dcom.ibm.websphere.logging.errheading=limited" as a
  generic JVM argument on the server process.
  
  The fix for this APAR is targeted for inclusion in fix packs
  8.5.5.23 and 9.0.5.14. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

• To get full headers prior to this APAR, create a JVM custom
  property on the server process named
  "com.ibm.websphere.logging.errheading" with value "full", or add
  "-Dcom.ibm.websphere.logging.errheading=full" as a generic JVM
  argument on the server process.
  

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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels