PH06642: BACK PORT DIAGNOSTIC PLAN TO 8.5.5.15

8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
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 new function.

Error description

• Back port diagnostic plan to 8.5.5.15
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server 8.5.5                                *
  ****************************************************************
  * 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 8.5.5.15.  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 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

• R850 PSY

     UP