Portlet configuration parameters for Portlet load monitoring

Portlet load monitoring has three configuration parameters related to portlets.

You set them as follows:
Maximum number of concurrent requests:
com.ibm.wps.pe.plm.maxrequest

Use this parameter to define the maximum number of concurrent requests that is allowed for a portlet. If the number of requests that the portlet serves at any time exceeds the maximum number of concurrent requests that you specify here, then Portlet load monitoring blocks further requests to this portlet. Instead of responding to the requests the portlet renders with a message stating that the portlet is not available. In order to re-enable this portlet for rendering, a portal administrator can enable the portlet by using the Manage Portlets administration portlet.

Example: To allow no more than a maximum of ten concurrent requests for a portlet, set the portlet preference com.ibm.wps.pe.plm.maxrequest to a value of 10 .

Reactivation limit of concurrent requests:
com.ibm.wps.pe.plm.minrequest

Use this parameter to define the reactivation limit for a portlet. Use this parameter for a recovery process. If Portlet load monitoring has blocked the portlet because it exceeded the maximum number of allowed concurrent requests, then no more requests to this portlet are allowed. If the portlet then completes its active requests after some time, the number of concurrent requests currently served by the portlet decreases. If the number of concurrent requests in the portlet falls back down to the reactivation limit that you specified for the portlet preference parameter com.ibm.wps.pe.plm.minrequest, Portlet load monitoring enables the portlet for responding to requests and rendering again. This setting is subject to two restrictions:

1. This setting is only evaluated when you have set the maximum number of concurrent requests by using the parameter com.ibm.wps.pe.plm.maxrequest above.

2. This value must be lower than the maximum number of concurrent requests that you entered for the parameter com.ibm.wps.pe.plm.maxrequest above.

Example 1: The portlet to be able to respond to requests again when it has no more than 3 active requests open, set the portlet preference parameter com.ibm.wps.pe.plm.minrequest to 3 .

Example 2: If you have set the maximum number of concurrent requests for a portlet to 10 by using the parameter com.ibm.wps.pe.plm.maxrequest and the reactivation limit of concurrent requests for the same portlet to 3 by using the parameter com.ibm.wps.pe.plm.minrequest , Portlet load monitoring works as follows:

1. When the portlet exceeds 10 and reaches 11 concurrent requests, Portlet load monitoring blocks the portlet from further requests.

2. When the portlet has completed 8 of the active requests and has only 3 active requests left to complete, Portlet load monitoring allows the portlet to respond to new incoming requests again.

Allowed average response time
com.ibm.wps.pe.plm.average.time.processing

Use this parameter to define the allowed average response time for the portlet, that is the time that the portlet takes to respond to an incoming request. Specify a value in milliseconds. If the portlet exceeds the average response time that you specified, then Portlet load monitoring blocks further requests to this portlet. In order to reenable this portlet for rendering, a portal administrator can enable the portlet by using the Manage Portlets administration portlet.

Example: To specify the average response time allowed for a portlet as 3 seconds, set the portlet preference com.ibm.wps.pe.plm.average.time.processing to a value of 3000 (milliseconds) for this portlet.

For information about setting the sample by which the average response time is calculated refer to the topic about Portal configuration parameters for Portlet load monitoring.

Parent

Pre-set portlet configuration parameters for Portlet load monitoring

 

+

Search Tips   |   Advanced Search