History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: UP-1423
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Unassigned
Reporter: Andrew Petro
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
uPortal

eagerly initialize portlet container

Created: 08/Feb/06 01:58 PM   Updated: 05/Mar/08 07:59 AM
Component/s: Portlet Container
Affects Version/s: None
Fix Version/s: 3.0.0-M5

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. Text File declareservlet.txt (1 kb)
2. Text File eagerinit.txt (26 kb)



 Description  « Hide
Troubleshooting an apparently deadlocked UW QA instance today, I'm seeing a lot of threads locked waiting for a chance to check if the portlet container has been initialzed. Currently CPortletAdapter lazily (but safely) initializes the portlet container. Maybe the portlet container should instead be eagerly initialzed (perhaps by a ContextListener?) and then CPortletAdapter instances could just assume it's already initialzed and not have to globally lock at channel instance provisioning time.

 All   Comments   Work Log   Change History      Sort Order:
Andrew Petro [13/Feb/06 03:23 PM]
Patch to web.xml declaring the eager portlet container initialization servlet.

Andrew Petro [13/Feb/06 03:24 PM]
Patch implementing the eager initialization.

Eric Dalquist [11/Dec/07 11:27 AM]
UP-1790 will resolve this issue.