I've been writing an application using LIME in Windows which works fine. However, I need to move it over to Linux. When I run more than one Lime agent on the same Linux host, it works. However, when I try it over two linux machines, or with one linux machine and a windows machine, it doesn't work. Basically blocking reads just block forever, unblocking reads return null.
This all works over two Windows machines, does anyone have any insight?
Thanks,
David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Problem solved, for anyone else who may encounter this, here's a reference:
On Red Hat Linux installations InetAddress.getLocalHost() may return an InetAddress corresponding to the loopback address (127.0.0.1). This arises because the default installation creates an association in /etc/hosts between the hostname of the machine and the loopback address. To ensure that InetAddress.getLocalHost() returns the actual host address the /etc/hosts file can be updated or the name service configuration file (/etc/nsswitch.conf) can be updated to query dns or nis before searching hosts.
Hey,
I've been writing an application using LIME in Windows which works fine. However, I need to move it over to Linux. When I run more than one Lime agent on the same Linux host, it works. However, when I try it over two linux machines, or with one linux machine and a windows machine, it doesn't work. Basically blocking reads just block forever, unblocking reads return null.
This all works over two Windows machines, does anyone have any insight?
Thanks,
David
I just got some additional insight into the problem:
Below is the output when I turned the debug option on (sorry should have done this before)
As you can see, its picking up the loopback address of the linux machine (127.0.0.1) instead of its real ip address. How can I fix this?
groupmgmt:SafeDistanceDetector: Discovered neighbor - [praxis/127.0.0.1:33393]
groupmgmt:SinglePhaseDisseminator: Enqueing connections from [chimpsky/122.33.10.12:3059] -
groupmgmt:SinglePhaseDisseminator: arriving - [[praxis/127.0.0.1:33393]]
groupmgmt:SinglePhaseDisseminator: departing - []
groupmgmt:SinglePhaseDisseminator: Processing arriving - [chimpsky/122.33.10.12:3059] connected to [praxis/127.0.0.1:33393]
groupmgmt:SinglePhaseDisseminator: Starting to process arrival
groupmgmt:SinglePhaseDisseminator: Sending GetLeaderMessage to new Member - [praxis/127.0.0.1:33393]
groupmgmt:SinglePhaseDisseminator: ! Failed to send message groupmgmt.impl.SPLeaderAddressMessage@69d02b to [praxis/127.0.0.1:33393] !
groupmgmt:SinglePhaseDisseminator: ! Failed to send message groupmgmt.impl.SPGetLeaderMessage@ae3364 to [praxis/127.0.0.1:33393] !
Problem solved, for anyone else who may encounter this, here's a reference:
On Red Hat Linux installations InetAddress.getLocalHost() may return an InetAddress corresponding to the loopback address (127.0.0.1). This arises because the default installation creates an association in /etc/hosts between the hostname of the machine and the loopback address. To ensure that InetAddress.getLocalHost() returns the actual host address the /etc/hosts file can be updated or the name service configuration file (/etc/nsswitch.conf) can be updated to query dns or nis before searching hosts.
http://java.sun.com/products/archive/j2se/1.4.0_04/networking-relnotes.html