[
https://issues.jboss.org/browse/AS7-4512?page=com.atlassian.jira.plugin.s...
]
Paul Ferraro resolved AS7-4512.
-------------------------------
Resolution: Rejected
The cluster name of a cache container (analogous to partition name) is already exposed via
the management API.
e.g.
/subsystem=infinispan/cache-container=cluster/transport=TRANSPORT:read-attribute(name=cluster)
As Rado mentioned, you wouldn't want to isolate your clusters via cluster name alone -
this would be done via distinct jgroups-udp multicast-address/port socket bindings.
Cluster partition name not exposed
----------------------------------
Key: AS7-4512
URL:
https://issues.jboss.org/browse/AS7-4512
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Reporter: Heiko Rupp
Assignee: Paul Ferraro
Labels: rhq
In previous versions of AS, the cluster partition name was exposed and user changeable.
Users expect to set that in order to build different clusters. This should be exposed r/w
in the management api.
See also
https://issues.jboss.org/browse/ISPN-1976
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira