Steven P. Heutinck wrote:
> Yes, I can confirm it does work. Make sure you are trying to bind to IP
> address of your primary network device i.e. eth0.
>
> Cheers,
> Steve
>
> John Collins wrote:
> >
> >... I can't get past the attempt to bind to the rmi registry. This
> > code works on both NT and Solaris, and has been exercised fairly
> > extensively. I was hoping to be able to jettison NT and move over to
> > Linux for further development.
> >
> > Here's what I've got:
> > -Red Hat Linux 5.0.
> > -libc 2.0.7 (I've tried downloading 2.0.7-7 a couple of times; it's
> > been very slow.)
> > -jdk1.1.5v7-glibc version
> >
> > I'm not sure how to proceed in debugging this. Here's the error message:
> >
> > -------------------
> > java.rmi.ServerException: Server RemoteException; nested exception is:
> > java.rmi.AccessException: Registry.rebind
> > -------------------
> > As far as I can figure out, I'm doing exactly the same thing here that I
> > do on Solaris to run this thing. The only part of it that isn't scripted
> > is the startup of the rmiregistry. On both systems I run this in my user
> > account.
Thanks, Steve -
Others have reported that my code works on their systems. It still doesn't
work on my system. What do you mean about "bind to IP address...". I don't
see any options for binding to IP addresses in either the rmiregistry command
or the Naming.rebind() method. It's in the rebind call that the problem
occurs, and it's definitely a different message than the one that happens
when I don't have rmiregistry running.
John Collins
