PK65928: ADD CONFIGURABLE THRESHOLD-BASED WARNING MESSAGES TO SERVLET, LRP AND RRP

6.0.1.7 Download: WebSphere Portal and Web Content Manager V6.0.1, fix pack 7
6.0.1.5 Download: WebSphere Portal and Web Content Management V6.0.1 fix pack 5

APAR status

• Closed as program error.

Error description

• When analysing performance problems within an environment, it
  is useful to have logging messages appear when a request takes
  longer than a defined threshold. Additionally, when processing
  requests on the WCM server (from either the Servlet, LRP or
  RRP), it would be useful to define warning thresholds for the
  RenderContext generation and Advanced-Cache processing time (if
  the Advanced-Cache is used).
  

Local fix

• No workaround is available.
  

Problem summary

• When analysing performance problems within an environment, it is
  useful to have logging messages appear when a request takes
  longer than a defined threshold. Additionally, when processing
  requests on the WCM server (from either the Servlet, LRP or
  RRP), it would be useful to define warning thresholds for the
  RenderContext generation and Advanced-Cache processing time (if
  the Advanced-Cache is used).
  

Problem conclusion

• The logging of the WCM product has been improved in the
  following ways:
  - Response time warning thresholds (in milliseconds) can now be
  set for the ConnectServlet, Local Rendering Portlet (LRP) and
  the Remote Rendering Portlet (RRP), where requests that take
  longer than the setting will be logged to the SystemOut.log. For
  the ConnectServlet, the setting is called
  'connect.responseTimeWarningThreshold' and is set in the
  <WPS_ROOT>\wcm\shared\app\config\ wcmservices\
  WCMConfigService.properties, whereas for the portlets, the
  setting is called 'responseTimeWarningThreshold' and is
  specified via the Portal Administration (eg.  Administration >
  Web Modules)
   - Note to display the querystring in the ConnectServlet, set
  'connect.logrequestparameters' to true in the
  WCMConfigService.properties file.
  
  - A RenderContext generation warning threshold (in milliseconds)
  can be set for all requests (whether they come from the Servlet,
  LRP or RRP). The setting is called
  'connect.renderContextTimeWarningThreshold' and is set in the
  <WPS_ROOT>\wcm\shared\app\config\ wcmservices\
  WCMConfigService.properties. When processing requests (when
  Servlet-Caching is not enabled), WCM must first generate its
  RenderContext before it can continue to either serve out a
  site-cached copy of the request OR process the request live,
  These messages will be print to the SystemOut.log
  
  - An Advanced-Cache processing warning threshold (in
  milliseconds) can be set for all requests (whether they come
  from the Servlet, LRP or RRP). The setting is called
  'connect.cacheProcessingTimeWarningThreshold' and is set in the
  <WPS_ROOT>\wcm\shared\app\config\ wcmservices\
  WCMConfigService.properties.
  
  An interim Fix is available for this APAR from Fix Central at:
  
  For release 6.0.1.3:
  
  http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde
  r?brandid=2&productid=Workplace%20Web%20Content%20Management&fix
  es=6.0.1.3-WCM-PK65928
  
  You will need to cut/paste the entire URL into a browser to
  resolve the address.
  

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

  WEBSPHERE PORTA

• Fixed component ID

  5724E7600

Applicable component levels

• R60A PSY

     UP