PM63082: MONITORING HPEL REPOSITORY WITH LOGVIEWER CAN FAIL TO SHOW EITHER LOG OR TRACE RECORDS WHEN -INSTANCE OPTION IS USED

8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• When monitoring a specific instance in HPEL repository for new
  log records using logViewer command line tool sometimes either
  log or trace records can be missing in the output.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
  *                  using logViewer to monitor server           *
  *                  activities in High Performance Extensible   *
  *                  Logging (HPEL) mode.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: When monitoring server activities       *
  *                      using the -instance option either log   *
  *                      or trace records could be missing in    *
  *                      the output.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If either the log or trace directory of a server instance was
  not present at the moment when monitoring started, records from
  that directory will be missing in the output. Also, if the log
  directory was created earlier than the trace directory and
  filtering caused all previous log records to be filtered out
  at the moment when monitoring starts, log records will be
  missing in output even after they appear in the log directory.
  Similar problem exists for the trace directory and trace
  records.
  

Problem conclusion

• The fix updates logic used in logViewer for monitoring the HPEL
  repository to locate both log and trace directories correctly.
  
  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 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