Issue

• In our JBoss EPP 4.3 environment we have a large number of users with dashboards. We noticed that when a newly created user accesses his dashboard for the first time, a lot of the following SQL selects are issued against the database:

  select portalobje0_.PK as PK64_0_, portalobje0_.LISTENER as LISTENER64_0_, portalobje0_4_.INSTANCE_REF as INSTANCE2_72_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 
  eft outer join JBP_PORTAL_WINDOW_STATE windowstat3_ on portalobje0_.PK=windowstat3_.PK 
  where portalobje0_.PK=?
  

This N+1 select problem results in bad performance when creating new dashboards with a large Portal user base.