Bug 794061 (JBEPP-1128) - Missing partition name in cache instance jcr.stack
Summary: Missing partition name in cache instance jcr.stack
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-1128
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal
Version: 5.1.1.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0.ER01
Assignee: hfnukal@redhat.com
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-29 07:33 UTC by Martin Weiler
Modified: 2012-02-28 16:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-13 09:02:58 UTC
Type: Bug


Attachments (Terms of Use)


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

Description Martin Weiler 2011-08-29 07:33:56 UTC
project_key: JBEPP

When starting EPP 5.1.1 in a clustered profile with a cluster partition name, there is one cache instance which does not include the partition name:

./bin/run.sh -c all -Dexo.profiles=cluster -g MyPartition

GMS: address is 127.0.0.1:55200 (cluster=MyPartition)
GMS: address is 127.0.0.1:55200 (cluster=MyPartition-HAPartitionCache)
GMS: address is 127.0.0.1:55200 (cluster=MyPartition-JMS-CTRL)
GMS: address is 127.0.0.1:7900 (cluster=MyPartition-JMS-DATA)
GMS: address is 127.0.0.1:60717 (cluster=MyPartition-gatein MOPSessionManager)
GMS: address is 127.0.0.1:55200 (cluster=MyPartition-opt-entity)
GMS: address is 127.0.0.1:55200 (cluster=MyPartition-timestamps)
GMS: address is 127.0.0.1:57300 (cluster=MyPartition-idm-api-cluster)
GMS: address is 127.0.0.1:45158 (cluster=MyPartition-idm-store-cluster)
GMS: address is 127.0.0.1:42082 (cluster=jcr.stack)
GMS: address is 127.0.0.1:55200 (cluster=MyPartition-SessionCache)

==> jcr.stack does not have the partition name!

Comment 1 Thomas Heute 2011-09-22 07:08:15 UTC
Release Notes Docs Status: Added: Not Required



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