Bug 793513 (JBEPP-594) - Cache portal config for the scope of the requess
Summary: Cache portal config for the scope of the requess
Keywords:
Status: CLOSED WONTFIX
Alias: JBEPP-594
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: unspecified
Version: 5.1.0.GA,5.1.1.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.1.GA
Assignee: mposolda
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-29 13:26 UTC by Prabhat Jha
Modified: 2012-03-26 04:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-30 16:53:42 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-594 0 None Closed Cache portal config for the scope of the requess 2012-04-19 20:21:21 UTC

Description Prabhat Jha 2010-10-29 13:26:15 UTC 
project_key: JBEPP

Please see https://jira.jboss.org/browse/GTNPORTAL-1610
Comment 1 Prabhat Jha 2010-10-29 13:26:45 UTC 
Link: Added: This issue depends GTNPORTAL-1610
Comment 2 hfnukal@redhat.com 2012-01-11 11:50:41 UTC 
Labels: Added: EPP_5_2_1_Candidate
Comment 4 Thomas Heute 2012-01-12 10:26:43 UTC 
Labels: Removed: EPP_5_2_1_Candidate
Comment 6 mposolda 2012-01-30 16:53:42 UTC 
Release Notes Docs Status: Removed: Not Required Added: Not Yet Documented
Release Notes Text: Added: Issue is outdated and probably it has been already fixed in 5.2.0 as well. So I am not sure if it needs to be documented or not, so I am adding status to "Not Yet Documented" for now. I am adding some info if needed.

PROBLEM: There was small performance problem that downloading some portal configuration objects from IDM and JCR database were repeated more times per HTTP single request. So it was not ideal because we had more redundant calls with same parameters.

CAUSED BY: Missing caching of UserPortalConfig object.

RESOLUTION: Now when PortalRequestContext.getUserPortalConfig is called first time per HTTP request, then UserPortalConfig object is cached. Other calls to PortalRequestContext.getUserPortalConfig within same HTTP request are using object from cache and they don't need to send another requests to persistent storages like IDM or JCR.
Comment 7 mposolda 2012-03-22 19:37:00 UTC 
Release notes not needed (I don't see "-" flag)
Note You need to log in before you can comment on or make changes to this bug.