Bug 1059053

+++ This bug was initially created as a clone of Bug #1059036 +++

Description of problem:

If you configure a richfaces portlet in dashboard template, the portlet may break for the first access by a newly created user.

How reproducible:

Not always. You can constantly reproduce it by using debugger.

Steps to Reproduce:

You need to use debugger to constantly reproduce the issue with richFacesPortlet.war. I think if use a simple richfaces portlet, you can easily reproduce without debugger.

- Deploy jboss-epp-5.2.2/portletbridge/examples/richFacesPortlet.war
- Edit gatein.ear/02portal.war/WEB-INF/conf/portal/user/template/user/pages.xml

<page-set xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.gatein.org/xml/ns/gatein_objects_1_0 http://www.gatein.org/xml/ns/gatein_objects_1_0"
        xmlns="http://www.gatein.org/xml/ns/gatein_objects_1_0">

        <!-- The default dashboard page -->
        <page>
                <name>Tab_Default</name>
                <title>Tab_Default</title>
        <portlet-application>
        <portlet>
                <application-ref>richFacesPortlet</application-ref>
                <portlet-ref>richFacesPortlet</portlet-ref>
        </portlet>
        <access-permissions>Everyone</access-permissions>
        <show-info-bar>false</show-info-bar>
        </portlet-application>
        </page>
</page-set>

- Start EPP
- Login as root
- [Application Registry]->[Import applications]
- Logout
- Login as john
- Set breakpoints at:
-- org.exoplatform.portal.application.PortalRequestHandler [line: 185] - processRequest(PortalRequestContext, PortalApplication)	
-- org.exoplatform.portal.application.UserSiteLifeCycle [line: 66] - onStartRequest(Application, PortalRequestContext)	
- Access to Dashboard
- The first request (Thread A) stops at UserSiteLifeCycle line 66. DataStorage cannot find PortalConfig so UserPortalConfigService.createUserSite() is called. It should persist the PortalConfig to JCR but *it's not committed yet*.
- Resume Thread A with debugger
- The request stops at PortalRequestHandler line 185. Portal responded to browser but JCR is not committed yet.
- Several requests (Thread B, C,...) from browser come into UserSiteLifeCycle line 66. "Step Over" Thread B to proceed 1 line. DataStorage cannot find PortalConfig yet so UserPortalConfigService.createUserSite() is called.
- Resume Thread A with debugger
- Turn off all breakpoints
- Resume all threads with debugger
- Those threads will throw NoSuchDataException at some point because the ID (PortletContext) is deleted during UserPortalConfigService.createUserSite()

Actual results:

- You will see the following ERROR message in server side

2014-01-22 11:24:29,989 ERROR [portal:UIPortletLifecycle] (http-0.0.0.0-8080-1) Portlet render threw an exception
org.exoplatform.services.portletcontainer.PortletContainerException: org.exoplatform.portal.config.NoSuchDataException: Can not find b7c32f74c0a80a8250131224537112e6
        at org.exoplatform.portal.webui.application.UIPortletLifecycle.processRender(UIPortletLifecycle.java:336)
        at org.exoplatform.portal.webui.application.UIPortletLifecycle.processRender(UIPortletLifecycle.java:62)
        at org.exoplatform.webui.core.UIComponent.processRender(UIComponent.java:144)
...
Caused by: org.exoplatform.portal.config.NoSuchDataException: Can not find b7c32f74c0a80a8250131224537112e6
        at org.exoplatform.portal.pom.config.POMSession.findCustomizationById(POMSession.java:214)
        at org.exoplatform.portal.pom.config.tasks.PreferencesTask$Load.run(PreferencesTask.java:91)
        at org.exoplatform.portal.pom.config.POMSession.execute(POMSession.java:405)
        at org.exoplatform.portal.pom.config.ExecutorDispatcher.execute(ExecutorDispatcher.java:60)
        at org.exoplatform.portal.pom.config.TaskExecutionDecorator.execute(TaskExecutionDecorator.java:38)
        at org.exoplatform.portal.pom.config.cache.DataCache.read(DataCache.java:208)
        at org.exoplatform.portal.pom.config.cache.DataCache.execute(DataCache.java:61)
        at org.exoplatform.portal.pom.config.TaskExecutionDecorator.execute(TaskExecutionDecorator.java:38)
        at org.exoplatform.portal.pom.config.cache.PortalNamesCache.execute(PortalNamesCache.java:77)
        at org.exoplatform.portal.pom.config.POMSessionManager.execute(POMSessionManager.java:253)
        at org.exoplatform.portal.pom.config.POMDataStorage.load(POMDataStorage.java:176)
        at org.exoplatform.portal.config.DataStorageImpl.load(DataStorageImpl.java:111)
        at org.exoplatform.portal.webui.application.ModelAdapter$1.getPortletContext(ModelAdapter.java:89)
        at org.exoplatform.portal.webui.application.UIPortlet.getPortletContext(UIPortlet.java:997)
        at org.exoplatform.portal.webui.application.UIPortlet.create(UIPortlet.java:833)
        at org.exoplatform.portal.webui.application.UIPortletLifecycle.processRender(UIPortletLifecycle.java:212)
        ... 146 more

- You may see some parts are broken in the portlet

Expected results:

Dashboard and its portlet are displayed without an issue