Bug 1080254

Summary: NoSuchDataException after adding a RF portlet to a page
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: Toshiya Kobayashi <tkobayas>
Component: PortalAssignee: Nobody <nobody>
Status: CLOSED UPSTREAM QA Contact: Tomas Kyjovsky <tkyjovsk>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.2.2.GACC: epp-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1080249 Environment:
Last Closed: 2025-02-10 03:35:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1080249    
Bug Blocks:    

Description Toshiya Kobayashi 2014-03-25 03:33:53 UTC
+++ This bug was initially created as a clone of Bug #1080249 +++

Description of problem:

Platform BZ for https://issues.jboss.org/browse/GTNPORTAL-2581

How reproducible:

Not always. A debugger helps to reproduce the issue constantly.


Steps to Reproduce:
1. Deploy richFacesPortlet.war
2. Import richFacesPortlet via Application Registry
3. Add an empty page ([Site Editor]->[Add New Page])
4. Edit the page ([Site Editor]->[Edit Page])
5. Drag&Drop richFacesPortlet
6. Attach a debugger and set a breakpoint at PortalRequestHandler.java line.212.
====
208       finally
209       {
210 
211          // We close the writer here once and for all
212          Safe.close(context.getWriter());
213 
214          //
215          try
216          {
217             for (ApplicationLifecycle lifecycle : lifecycles)
218                lifecycle.onEndRequest(app, context);
219          }
====
7. Click save icon in portal
8. Debugger stops at PortalRequestHandler line.212.
9. Disable the breakpoint and 'step over' the execution in debugger
10. Then 'resume' the debugger


Actual results:

2014-03-19 11:53:17,875 ERROR [portal:UIPortletLifecycle] (http-0.0.0.0-8080-27) Portlet render threw an exception
org.exoplatform.services.portletcontainer.PortletContainerException: org.exoplatform.portal.config.NoSuchDataException: Can not find d841cbfbc0a8088319ce667f85f0bfcd
        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)
        at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:368)
        at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:358)
        at sun.reflect.GeneratedMethodAccessor501.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:229)
        at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:52)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120)
        at UIPage.run(UIPage.gtmpl:8)
...

Expected results:

The page is properly rendered with the portlet

Comment 2 Red Hat Bugzilla 2025-02-10 03:35:26 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.