IBM Support

PI97338: WEBSPHERE APPLICATION SERVER DIAGNOSTIC PLAN

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as new function.

Error description

  • A new Serviceability feature to help L2/L3 diagnose
    intermittent customer issues and addresses the issue where
    customers do not want to enable trace in their production
    systems.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Version 9.0                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Difficult to diagnose intermittent      *
    *                      issues on WebSphere Application         *
    *                      Server.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When an intermittent issue occurs in WebSphere Application
    Server, it becomes hard to diagnose as it is hard to capture
    trace-buffer/javacores/heapdumps manually at the right time.
    Enabling trace for extended periods of time to capture
    intermittent issues may cause the trace.log files to roll
    over, as well as, affect the overall performance.
    

Problem conclusion

  • A new serviceability function, called Diagnostic Plan, is added
    to help diagnose intermittent issues and address the issue
    where users do not want to enable trace in their production
    systems.
    
    The diagnostic plan is a MBean API, which can be invoked
    by jython scripts using the wsadmin command. This will set up a
    diagnostic plan for the WebSphere Application Server to follow.
    
    The plan are simple sequence of actions that can wait for
    specific log, trace, or FFDC events to occur, and can trigger
    the modification of the trace spec, collecting the trace
    buffer content, collecting javacores, collecting heap dumps,
    or collecting system cores.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 9.0.0.8.  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

    PI97338

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-04-30

  • Closed date

    2018-06-13

  • Last modified date

    2018-06-13

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 900

Reference #: PI97338

Modified date: 13 June 2018


Translate this page: