PH22112: DISPLAY WORK WITH ZOSREQUESTLOGGING FEATURE DOESN'T COUNT SERVLET REQUESTS

APAR status

• Closed as program error.

Error description

• The servlet request work counts are reported as zero when
  the
  server is started with zosRequestLogging feature.
  DISPLAY WORK command reports the servlet request counts
  correctly if the server is started without zosRequestLogging
  feature.
  

Local fix

• na
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty for z/OS                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: z/OS display,work modify command does   *
  *                      NOT count servlet requests if feature   *
  *                      zosRequestLogging is enabled            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The z/OS modify command to display work counts, "f
  <server>,display,work", may return zeroes for the count values
  if the zosRequestLogging feature is enabled:
  
    <feature>requestTiming-1.0</feature>
    ...
    <feature>zosRequestLogging-1.0</feature>
  
  The problem is that when the server is started with the
  zosRequestLogging feature, the counts are reported as zero.
  Also, if the server is started without the zosRequestLogging
  feature, then processes a set of servlet requests, then the
  zosRequestLogging feature is dynamically enabled, and the server
  processes more servlet requests, the request counts will stay
  the same as they were prior to enabling the zosRequestLogging
  feature.
  
  The counts are based on probe root events.  The probe
  infrastructure setting of the root event is influenced and set
  by probe implementations along the execution path.  The reason
  for the missing counts with the zosRequestLogging feature
  enabled is that a new probe root event was established.  The
  related counts were accumulated in a different location.
  

Problem conclusion

• Code has been modified when collecting the request counts to use
  multiple probe root events.  It will use the one established
  when only the requestTiming feature is enabled and the probe
  root event established when the zosRequestLogging feature is
  enabled.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 20.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

  LIBERTY PROF -

• Fixed component ID

  5655W6514

Applicable component levels

• RCD0 PSY

     UP