Affects Version/s: 3.1.2_b14
Fix Version/s: None
Initially discovered on Linux 2.6.18-18.104.22.168.1.el5 #1 SMP Thu Sep 3 00:21:28 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
Confirmed also to occur on Windows XP
Did not occur on dual stack Mac OS X 10.6.8 or IPv4 only Solaris 5.10.
Specifying network interface "eth0" on linux OS is not working correctly. (confirmed same failure on Windows)
Specified this issue as minor since documentation does not state that it is valid to specify a network interface
name for gms-bind-interface-address. This capability was added to assist in machine network configuration setups
where some machines are multihomed and we were not consistently selecting appropriate network interface on all machines
in cluster. Specifying the network interface for the cluster to use bypasses the automated selection of the first network address to use.
The binding address returned by InetAddress.getByName() is returning "eth0/127.0.0.1".
The loopback interface is not appropriate for GMS inter-machine commmunications (only
when all instances are on one machine, only used for development.)
com.sun.enterprise.mgmt.transport.NetworkUtility identifies this issue exists.
%java -classpath shoal-gms-impl.jar com.sun.enterprise.mgmt.transport.NetworkUtility
Display name: eth0
Supports multicast? true
Hardware address: [0, 35, -117, 100, 122, 86]
Network Inet Address (preferIPV6=false) /10.133.184.160
Network Inet Address (preferIPV6=true) /fe80:0:0:0:223:8bff:fe64:7a56%7
resolveBindInterfaceName(eth0)=127.0.0.1 /* this value should be 10.133.184.160 */
This issue did not occur on Mac or Solaris.