IBM Support

PM60913: INTRODUCE ABILITY TO USE JAVA THREAD ID IN LOGS INSTEAD OF LOGRECORD THREAD ID.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • WebSphere Application Server logs report thread id retrieved
    from LogRecord instances. This ID is difficult to match with
    IDs used in Java core dumps.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
    *                  required to match threads reported in log   *
    *                  files with threads reported in Java core    *
    *                  dumps                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Thread id reported in WebSphere         *
    *                      Application Server log files            *
    *                      is different than identification used   *
    *                      for Java Thread instances.              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Thread id reported in WebSphere Application Server log files
    is retrieved from LogRecord instances which use their own
    thread identification schema different from identification used
    in Java Thread instances themselves. Log files reporting
    the same thread id as used in Java Thread instances will ensure
    that a thread where a log record was generated can be matched
    to a thread reported in a Java core dump.
    

Problem conclusion

  • This change introduced new System property
    "com.ibm.websphere.logging.useJULThreadID" controlling thread
    id type used in WebSphere Application Server log files. Value
    "true" for this property means that LogRecord instances is
    used to retrieve thread id. Value "false" means that Thread
    instance is used to retrieve thread id instead. If this
    system property is not set, value "true" is assumed.
    
    For information on setting JVM custom properties, refer to the
    Information Center article titled "Java virtual machine custom
    properties" for your version and release of WebSphere
    Application Server.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.0.4.  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 number

    PM60913

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-03-21

  • Closed date

    2012-04-18

  • Last modified date

    2012-04-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

  • R800 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 8.0

Reference #: PM60913

Modified date: 18 April 2012