Bug 794121 (JBEPP-1187)

Summary: Replication error when login user (cluster profile)
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: mposolda
Component: unspecifiedAssignee: Default User <jbpapp-maint>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.2.0.ER01, 5.2.0.ER02CC: epp-bugs, mvanco
Target Milestone: ---   
Target Release: 5.2.0.ER03   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-1187
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-10 06:34:20 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:
Attachments:
Description Flags
exception-loginUser-clusterProfile.txt
none
cluster-templates.txt
none
cluster-templates.png none

Description mposolda 2011-09-19 06:50:00 UTC
project_key: JBEPP

- Start EPP 5.2.ER1 with command: ./run.sh -c all -Dexo.profiles=cluster
- Login as mary
- Now exception in server log (See attachement)

Comment 1 mposolda 2011-09-19 06:51:29 UTC
Attachment: Added: exception-loginUser-clusterProfile.txt


Comment 2 mposolda 2011-09-19 06:52:33 UTC
Link: Added: This issue is related to JBQA-5399


Comment 3 mposolda 2011-09-19 06:54:50 UTC
Link: Added: This issue is related to GTNPORTAL-2109


Comment 4 Michal Vanco 2011-10-07 16:15:57 UTC
Reopening.
Issue still present at 5.2.0 ER02.
I've only started clean portal by:
sh run.sh -c all -Dexo.profiles=cluster
and when I opened localhost:8080/portal, error was thrown in log.

Comment 6 Thomas Heute 2011-10-10 06:34:20 UTC
Release Notes Docs Status: Added: Not Required


Comment 7 Michal Vanco 2011-10-10 16:43:04 UTC
Implication of this error is that all groovy templates are not rendered properly after replication. NPE is thrown when calling org.exoplatform.commons.cache.future.FutureExoCache.get(FutureExoCache.java:57).
Important: this behavior is present at 2-node cluster (not on singlenode)

Comment 8 Michal Vanco 2011-10-10 16:43:04 UTC
Attachment: Added: cluster-templates.txt
Attachment: Added: cluster-templates.png