PI50828: WLM SUPPORT IS IGNORED WHEN RUNNING Z/OS CONNECT IN ASYNC MODE

APAR status

• Closed as program error.

Error description

• The problem is there is *NO* WLM support when processing
  HTTP
  requests through z/OS Connect when it is configured to run
  in
  asynchronous mode. Asynchronous mode processing is the
  default.
  In this case requests run without an enclave. CPU time used
  to
  handle a given HTTP request is not recorded against the
  current
  enclave that represents that enclave being invoked.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty for z/OS                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: All CPU time for work processed by an   *
  *                      asynchronous servlet is not recorded    *
  *                      when using the zosWlm-1.0 feature.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  All CPU time for work processed by an asynchronous servlet is
  not recorded when using zosWlm-1.0 feature. More precisely, the
  asynchronous part of a the workload being processed by
  asynchronous servlets is not recorded with WLM. If a WLM report,
  that tracks that particular workload, is obtained, it will
  incorrectly show a minimal amount of CPU time spent executing
  the workload.
  

Problem conclusion

• Updates were made to allow the asynchronous part of work
  processed by an asynchronous servlet to be captured and recorded
  with WLM.
  
  To ensure proper work tracking, when using the servlet-3.0
  feature, users MUST set the transfercontextinasyncservletrequest
  attribute to true under the webContainer element in the server's
  configuration file. For example:
  
  <webContainer transfercontextinasyncservletrequest="true"/>
  
  Setting the transfercontextinasyncservletrequest attribute is
  not needed when using the servlet-3.1 feature.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 17.0.0.1.  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

• R850 PSY

     UP