?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] <[email protected]> on behalf of James Wennmacher <[email protected]> Sent: Tuesday, August 26, 2014 11:00 AM To: [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 -- 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
