Bug 1083433 - UIContainer is not thread-safe
Summary: UIContainer is not thread-safe
Keywords:
Status: NEW
Alias: None
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal
Version: 5.2.2.GA
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Tomas Kyjovsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-02 09:07 UTC by Toshiya Kobayashi
Modified: 2020-04-27 01:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker GTNPORTAL-2571 0 Major Resolved UIContainer is not thread-safe 2014-04-03 01:52:40 UTC

Description Toshiya Kobayashi 2014-04-02 09:07:01 UTC
Description of problem:

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

Steps to Reproduce:

- Login as root
- Go to dashboard
- Keep pressing F5 for 10 seconds

Actual results:

09:02:47,951 ERROR [PortletApplicationController] Error while rendering the porlet
org.exoplatform.groovyscript.TemplateRuntimeException: Groovy template exception at DataText[pos=Position[col=1,line=11],data=          uicomponent.renderChild(UIDashboard.class);] for template app:/groovy/dashboard/webui/component/UIDashboardPortlet.gtmpl
    at org.exoplatform.groovyscript.GroovyScript.buildRuntimeException(GroovyScript.java:178)
...
Caused by: java.util.ConcurrentModificationException
    at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
    at java.util.AbstractList$Itr.next(AbstractList.java:343)
    at UIColumnContainer.run(UIColumnContainer.gtmpl:7)
    at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:111)
    at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:118)
    at org.exoplatform.groovyscript.text.TemplateService.merge(TemplateService.java:117)

As this keeps reloading, finally it will render a correct page so not a problem from user perspective.

Expected results:

No Exception


Note You need to log in before you can comment on or make changes to this bug.