Bug 793439 (JBEPP-523) - Cluster channel name are same for all Portal workspaces
Summary: Cluster channel name are same for all Portal workspaces
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-523
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: unspecified
Version: 5.1.0.ER01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0.ER02
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-04 11:58 UTC by Thomas Heute
Modified: 2010-11-09 05:51 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-05 08:35:08 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-523 0 None None None Never

Description Thomas Heute 2010-10-04 11:58:08 UTC 
project_key: JBEPP
Comment 1 Thomas Heute 2010-10-04 11:58:23 UTC 
Link: Added: This issue is related to GTNPORTAL-1526
Comment 2 Scott Mumford 2010-11-09 05:51:57 UTC 
Release Notes Docs Status: Added: Documented as Resolved Issue
Release Notes Text: Added: The JCR Lock Manager in previous releases of EPP was configured to use the same channel name in all workspaces.
For example:
The 'portal-system' channel name was:
<property name="jbosscache-cluster-name" value="jcrlock-${container.name.suffix}-system" />
Instead of:
<property name="jbosscache-cluster-name" value="jcrlock-${container.name.suffix}-portal-system" />

This naming convention could allow data changes to affect the incorrect workspace.

The repository-configuration.xml file has been updated to resolve this issue.
Note You need to log in before you can comment on or make changes to this bug.