IBM Support

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

Subscribe

You can track all active APARs for this component.

 

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 number

    PI15653

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-04-09

  • Closed date

    2014-06-18

  • Last modified date

    2014-06-18

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022