[jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1249) Increase the cache timeout value to 30 mns instead of 2 mns

[Julien Viet (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1249?page=all ]

Julien Viet updated JBPORTAL-1249:
----------------------------------

          Summary: Increase the cache timeout value to 30 mns instead of 2 mns  (was: optimize number of DB calls when a simple portlet page is hit)
    Fix Version/s: 2.6.Beta1
         Priority: Minor  (was: Major)

> Increase the cache timeout value to 30 mns instead of 2 mns
> -----------------------------------------------------------
>
>                 Key: JBPORTAL-1249
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1249
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.Alpha2
>            Reporter: Prabhat Jha
>         Assigned To: Julien Viet
>            Priority: Minor
>             Fix For: 2.6.Beta1
>
>
> Assuming that following queries have already been optimized, can we reduce these DB calls and queries which are being made for every hit to the page?  The URL that gets hit is http://localhost:8080/portal/portal/default/NullPortletPage
> 1.       I see "[org.hibernate.jdbc.ConnectionManager] opening JDBC connection" getting printed 35 times.
>  
> 2.       This  query is made 27 times. select objectnode0_.PK as PK56_1_, objectnode0_.PATH as PATH56_1_, objectnode0_.NAME as NAME56_1_, objectnode0_.PARENT_KEY as PARENT4_56_1_, securityco1_.NODE_KEY as NODE3_3_, securityco1_.PK as PK3_, securityco1_.ROLE as ROLE3_, securityco1_.PK as PK65_0_, securityco1_.ROLE as ROLE65_0_, securityco1_.NODE_KEY as NODE3_65_0_, actions2_.PK as PK4_, actions2_.ACTIONS as ACTIONS4_ from JBP_OBJECT_NODE objectnode0_ left outer join JBP_OBJECT_NODE_SEC securityco1_ on objectnode0_.PK=securityco1_.NODE_KEY left outer join JBP_OBJECT_NODE_SEC_ACTIONS actions2_ on securityco1_.PK=actions2_.PK where objectnode0_.PK=?
>  
> 3.       This  query is made 8 times:  select portalobje0_.PK as PK57_0_, portalobje0_.LISTENER as LISTENER57_0_, portalobje0_4_.INSTANCE_REF as INSTANCE2_64_0_, case when portalobje0_1_.PK is not null then 1 when portalobje0_2_.PK is not null then 2 when portalobje0_3_.PK is not null then 3 when portalobje0_4_.PK is not null then 4 when portalobje0_.PK is not null then 0 end as clazz_0_, declaredpr1_.OBJECT_KEY as OBJECT1_2_, declaredpr1_.jbp_VALUE as jbp2_2_, declaredpr1_.NAME as NAME2_, modes2_.PK as PK3_, modes2_.name as name3_, windowstat3_.PK as PK4_, windowstat3_.name as name4_ from JBP_PORTAL_OBJECT portalobje0_ left outer join JBP_CONTEXT portalobje0_1_ on portalobje0_.PK=portalobje0_1_.PK left outer join JBP_PORTAL portalobje0_2_ on portalobje0_.PK=portalobje0_2_.PK left outer join JBP_PAGE portalobje0_3_ on portalobje0_.PK=portalobje0_3_.PK left outer join JBP_WINDOW portalobje0_4_ on portalobje0_.PK=portalobje0_4_.PK left outer join JBP_PORTAL_OBJECT_PROPS declaredpr1_ on portalobje0_.PK=declaredpr1_.OBJECT_KEY left outer join JBP_PORTAL_MODE modes2_ on portalobje0_.PK=modes2_.PK left outer join JBP_PORTAL_WINDOW_STATE windowstat3_ on portalobje0_.PK=windowstat3_.PK where portalobje0_.PK=?
>  
> 4.        select children0_.PARENT_KEY as PARENT4_1_, children0_.PK as PK1_, children0_.NAME as NAME1_, children0_.PK as PK56_0_, children0_.PATH as PATH56_0_, children0_.NAME as NAME56_0_, children0_.PARENT_KEY as PARENT4_56_0_ from JBP_OBJECT_NODE children0_ where children0_.PARENT_KEY=?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira