Portlet load monitoring allows WebSphere Portal administrators to protect their portal by limiting the number of concurrent requests and the average response time allowed for JSR 168 or JSR 286 portlets. If a portlet exceeds either the defined maximum number of concurrent requests, or the average response time, then Portlet Load Monitoring no longer allows further requests by the portlet. Instead, the portal renders the portlet as unavailable, and the portlet code is no longer called for further requests. This way, the portal installation is protected from non-responsive portlets consuming an increasing number of threads.
Note: Portlet load monitoring monitors JSR 168 and JSR 286 portlets only.
You will have to follow these steps in order to use portlet load monitoring
- Enable portlet load monitoring at the portal server level
- Set preferences at portlet level for following things. You can set the preferences at development time by adding values in portlet.xml or you can use "Manage portlets" portle to set preferences during runtime
- Number of concurrent request
- Maximum time allowed inside portlet
Once the portlet load monitoring is enabled you can use the portal admin console to check if the portlet is being monitored then use it to either manually block a monitored portlet or manually unblock a portlet blocked by portlet monitoring tool