[
https://issues.jboss.org/browse/AS7-3023?page=com.atlassian.jira.plugin.s...
]
Paul Ferraro commented on AS7-3023:
-----------------------------------
I don't think the JGroups subsystem is the appropriate location for this
configuration. This type of configuration should really reside in host.xml. The JGroups
and Infinispan subsystems should then be able to reference the proximity information from
the configure socket bindings or similar.
Move topology information to JGroups subsystem
----------------------------------------------
Key: AS7-3023
URL:
https://issues.jboss.org/browse/AS7-3023
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.0.Beta1b
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 7.1.0.Final
In order to support topology aware clusters, the addresses generated by MuxChannel must
be of type TopologyUUID, otherwise Infinispan cannot compare address topology (this
currently generates a ClassCastException). Also topology must be set before the channel is
started. For this reason the topology tuple (site,rack,machine) should be set at the
jgroups subsystem transport configuration and the Infinispan subsystem should merely
retrieve it from there.
--
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