[jboss-jira] [JBoss JIRA] (AS7-4512) Cluster partition name not exposed

Mon Apr 16 16:45:18 EDT 2012

    [ https://issues.jboss.org/browse/AS7-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12684686#comment-12684686 ] 

Paul Ferraro commented on AS7-4512:
-----------------------------------

1. In the TCP case, cluster communication is unicast only - so cluster "isolation" is less of an issue - since cluster membership is explicit, either defined statically or via a specific discovery method (e.g. S3_PING for EC2).  Note that the default tcp stack uses multicast for discovery (i.e. MPING), so isolated clusters would still want to use distinct multicast address/ports, defined via the jgroups-mping socket binding.

2. If undefined, the "cluster" attribute defaults to the cache container name.

> 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