PI15653: THE BINARY TRACE FACILITY'S TRACE COMMAND SOMETIMES DOES NOT DISPLAY THE CORRECT VALUE FOR SOME STRING FIELDS, AND ALSOSOM

8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• The binary trace facility writes common strings to the
  "objects" file and then writes the index of that string to the
  btrace logs.  There are certain occasions in which the ODR or
  other process which writes the trace records can write the logs
  with the incorrect index, which means when the trace command
  displays the trace record, it may display the wrong value for
  the string.  If you stop the process, delete the "objects" file
  and btrace.* files, then start the process, the records are
  correct. However, when the process is restarted using the
  existing "objects" file, the indices can be corrupted.  The fix
  for this problem ensures that the indices are always the same.
  After applying this i-fix, it is recommended that you delete
  your "objects" and "btrace.*" files from your logs directories
  one time only.  The newly generated objects and btrace files
  will be correct.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM Websphere Virtual          *
  *                  Enterprise versions 7.0.0.4, 8.5.5.2        *
  *                  and lower who try to read btrace using      *
  *                  trace command                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: The trace read output of btrace shows   *
  *                      incorrect values for certain trace      *
  *                      records such as                         *
  *                      http.request.affinity.cookie            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This problem is caused by incorrect writing of index by ODR and
  other processes in certain occassions.
  

Problem conclusion

• Changes have been made in the code to write the correct index.
  This issue will be resolved in the next available fix pack for
  WebSphere Virtual Enterprise V.7.0.0 and V8.5.5
  

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

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP

• R850 PSY

     UP