[gatein-issues] [JBoss JIRA] (GTNPORTAL-2072) NoSuchDataException is thrown after importing pages through export/import tool.

[Trong Tran (JIRA)]

     [ https://issues.jboss.org/browse/GTNPORTAL-2072?focusedWorklogId=12430197&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-12430197 ]

Trong Tran logged work on GTNPORTAL-2072:
-----------------------------------------

                Author: Trong Tran
            Created on: 12/Nov/13 2:09 AM
            Start Date: 11/Nov/13 5:08 AM
    Worklog Time Spent: 2 hours 
      Work Description: Investigate to define the solution

Issue Time Tracking
-------------------

    Remaining Estimate: 6 hours  (was: 1 day)
            Time Spent: 2 hours
            Worklog Id:     (was: 12430197)


> NoSuchDataException is thrown after importing pages through export/import tool.
> -------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-2072
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2072
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.2.0-Beta01
>            Reporter: Nick Scavelli
>            Assignee: Vu Viet Phuong
>              Labels: import
>   Original Estimate: 1 day
>          Time Spent: 2 hours
>  Remaining Estimate: 6 hours
>
> Below exception is thrown after importing pages through management tools (see steps to reproduce section).  I think this is a stale storageId coming from the UI when the data has changed outside the UI.  Typically logging out solves the issue, but this isn't optimal.  Changes to data should not be only achievable through the UI.  The changes are being sent through DataStorage, so there should be someway to sync this data up.
> Stacktrace:
> {noformat}
> Caused by: org.exoplatform.portal.config.NoSuchDataException: Can not find 1c42bec77f0000011076449207f5d085
> 	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:169)
> 	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:251)
> 	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:993)
> 	at org.exoplatform.portal.webui.application.UIPortlet.create(UIPortlet.java:829)
> 	at org.exoplatform.portal.webui.application.UIPortletLifecycle.processRender(UIPortletLifecycle.java:212)
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira