If you are or you have tried installing a Liferay on a cluster of Ubuntu machines and are/were having problems with the ehCache, do this check:]$ ping `hostname`
If it responds using an address on the loopback device, there's your problem.
By default, Ubuntu defines the machine's hostname on the loopback address (127.0.1.1), and since ehCache uses:InetAddress.getLocalHost().getHostAddress()
to resolve the address used in association with the RMICachePeers it creates, these peers will have addresses of 127.0.1.1:port which will render them unreachable to other peers on the network.
Here is a successful test:
rotty@liferay-laptop:~$ ping `hostname`
PING liferay-laptop (192.168.0.243) 56(84) bytes of data.
64 bytes from liferay-laptop (192.168.0.243): icmp_seq=1 ttl=64 time=0.046 ms
64 bytes from liferay-laptop (192.168.0.243): icmp_seq=2 ttl=64 time=0.056 ms
64 bytes from liferay-laptop (192.168.0.243): icmp_seq=3 ttl=64 time=0.055 ms
Note that the address is one on the private subnet where the rest of the cluster nodes can see it.
FYI!

