You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "David Sean Taylor (JIRA)" <je...@portals.apache.org> on 2013/07/27 02:01:48 UTC
[jira] [Resolved] (JS2-1287) Complete Implementation of Portlet
Tracking
[ https://issues.apache.org/jira/browse/JS2-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Sean Taylor resolved JS2-1287.
------------------------------------
Resolution: Fixed
> Complete Implementation of Portlet Tracking
> -------------------------------------------
>
> Key: JS2-1287
> URL: https://issues.apache.org/jira/browse/JS2-1287
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Aggregation
> Reporter: David Sean Taylor
> Assignee: David Sean Taylor
> Priority: Minor
> Fix For: 2.2.3
>
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> The Portlet Tracking Manager will track portlets rendering statistics, taking portlets out of
> service when their rendering time exceeds a configurable threshold. This threshold has two parameters:
> defaultPortletTimeout is a value in milliseconds representing the maximum render time to be considered
> as a timeout for a given portlet window. outOfServiceLimit represents the number of times the portlet window
> reaches the timeout threshold before it is taken out of service.
> This service is used primarily by the rendering engine to determine whether to take a portlet window out of
> service to avoid long 'timeouts' when rendering a portlet. The service also provides functions to put the
> portlet windows back into service.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org