Ahhh.  That helps.  Thanks for the context!

James Wennmacher - Unicon
480.558.2420

On 08/26/2014 10:11 AM, Eric Dalquist wrote:
> It was there to deal with portlets that are slow to warm up. The 
> default config appears to multiply the portlet's configured timeout by 
> 20 the first 5 times it executes. The key appears to be the portlet 
> descriptor so even if you have the same portlet (web proxy for 
> example) published 20 times only the first 5 renders of ANY WPP will 
> get the extra time.
>
> https://github.com/Jasig/uPortal/blob/master/uportal-war/src/main/java/org/jasig/portal/portlet/rendering/PortletExecutionManager.java#L112
> https://github.com/Jasig/uPortal/blob/master/uportal-war/src/main/java/org/jasig/portal/portlet/rendering/PortletExecutionManager.java#L105
>
>
> On Tue, Aug 26, 2014 at 9:15 AM, Andrew Petro <[email protected] 
> <mailto:[email protected]>> wrote:
>
>     ​James,
>
>
>     I don't *know* and I have not yet looked at the code in response
>     to this email.
>
>
>     I *suspect* that this is going to end up being about the very
>     interesting case where though a portlet has missed its timeout
>     window to render *for this response* there is nonetheless value in
>     allowing it to complete rendering and thereby populate caches in
>     support of subsequent requests and there's risk in prematurely
>     arresting its thread.
>
>
>     Perhaps that helps.
>
>
>     Kind regards,
>
>
>     Andrew
>
>
>     ------------------------------------------------------------------------
>     *From:* [email protected]
>     <mailto:[email protected]>
>     <[email protected]
>     <mailto:[email protected]>> on behalf of
>     James Wennmacher <[email protected]
>     <mailto:[email protected]>>
>     *Sent:* Tuesday, August 26, 2014 11:00 AM
>     *To:* [email protected]
>     <mailto:[email protected]>
>     *Cc:* Eric Dalquist
>     *Subject:* [uportal-dev] PortletExecutionManager and
>     extendedTimeoutExecutions
>     Hi  everyone,
>
>     Can someone with a bit of history explain what
>     extendedTimeoutExecutions in PortletExecutionManager (
>     
> https://github.com/Jasig/uPortal/blob/master/uportal-war/src/main/java/org/jasig/portal/portlet/rendering/PortletExecutionManager.java#L814)
>     is used for?  Why would a portlet run for a multiple of
>     extendedTimeoutExecutions instead of just its configured timeout
>     value?
>
>     Thanks,
>
>     -- 
>     James Wennmacher - Unicon
>     480.558.2420  <tel:480.558.2420>
>
>     -- 
>
>     You are currently subscribed [email protected]  
> <mailto:[email protected]>  as:[email protected]  
> <mailto:[email protected]>
>     To unsubscribe, change settings or access archives, 
> seehttp://www.ja-sig.org/wiki/display/JSG/uportal-dev
>
>     -- 
>
>     You are currently subscribed [email protected]  
> <mailto:[email protected]>  as:[email protected]  
> <mailto:[email protected]>
>
>     To unsubscribe, change settings or access archives, 
> seehttp://www.ja-sig.org/wiki/display/JSG/uportal-dev
>
>
> -- 
>
> You are currently subscribed to [email protected] as: 
> [email protected]
> To unsubscribe, change settings or access archives, see 
> http://www.ja-sig.org/wiki/display/JSG/uportal-dev


-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Reply via email to