[
https://jira.jboss.org/browse/JBAS-8710?page=com.atlassian.jira.plugin.sy...
]
Paul Ferraro commented on JBAS-8710:
------------------------------------
I reverted the change from my previous comment - we can't replace the string
comparison with InetAddress/port comparison, since the preferredMaster property refers to
the id of the ClusterNode (representing the host/port of the service) which is not
technically synonymous with the address/port of the jgroups transport.
HASingleton PreferredMasterElectionPolicy failing with IPv6
addresses
---------------------------------------------------------------------
Key: JBAS-8710
URL:
https://jira.jboss.org/browse/JBAS-8710
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering, Test Suite
Affects Versions: 6.0.0.CR1
Reporter: Richard Achmatowicz
Assignee: Paul Ferraro
Fix For: 6.0.0.Final
The bean org.jboss.ha.singleton.PreferredMasterElectionPolicy has an attribute
preferredMaster which identified a process in a cluster which should be the master node in
a clustered partition.
The preferred master attriubute is specified in the form host:port.
This format works fine for IPv4 addresses, but breaks down for IPv6 addresses unless the
host part is surrounded with square brackets, according to rfc2732.
There are two places which above class may break:
(i) in setting the preferred master attribute
(ii) in comparing ClusterNode instances using PreferredMasterElectionPolicy.find() to
check if a given preferred master is in the current cluster.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira