| Summary: | Cluster channel name are same for all Portal workspaces | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Thomas Heute <theute> |
| Component: | unspecified | Assignee: | Default User <jbpapp-maint> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.1.0.ER01 | ||
| Target Milestone: | --- | ||
| Target Release: | 5.1.0.ER02 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBEPP-523 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-10-05 08:35:08 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: | |
|
Description
Thomas Heute
2010-10-04 11:58:08 UTC
Link: Added: This issue is related to GTNPORTAL-1526 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.
|