howeee wrote:
> Hi,
>
> Just ran across something from jdk1.2 concerning
> InetAddress.getLocalHost()
>
> This is always returning 127.0.0.1. I looked at the bug reports from
> previous jdk releases and it appears that this was a bug and was corrected,
> but it appears to have "cropped up" again. Does anyone know of a work around
> for this?
>
Put your hostname info in the first line of hosts. Which should look like the
example, even if you use DNS, most likely your seq. will be files dns.
192.168.1.1 myhost myhost.domaine.com
127.0.0.1 localhost
.....
>
> The rmiregistry is doing the same thing and the only rmi client that can
> connect to my rmi server is a "locally run" rmi client. Is there any type of
> a work around to get the rmiregistry to accept remote clients.
>
The simple answer is no.
There was a mail on the rmi-users list from Brian who stated that he extended
rmiregistry to get around this.
"Others" have written a registry service based on servlets (jserv), which is
pretty
simple to do, and apache scales better than rmiregistry.
You might also want to take a look at Jini, for this. Jini should be the best
solution so far since it includes leases which makes the system more reliable.
I used to start services from jserv on different machines on demand with
fallbacks if one or more of the back-end servers failed. You can make such
a solution pretty reliable, but it requires knowledge and training of the
maintenance group specially if you throw in some load balancing.
I'm playing with a combination of both (Jini and Jserv), to make it scale and
easy to maintain and simple to understand
>
> Note: This appears to work on NT, but not Linux. Have not tested on Solaris
> yet.
>
It should not work on NT either, at least on my NT systems it doesn't.
Hope this helps,
Ronald
>
> Thanks in advance!!!
>
> howeee
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
