Works for me with jdk1.1.5v7 (didn't touch your stuff, just ran it):
-----
[user@ravel rmi-prob]$ java jec.ServerImpl &
[2] 5952
[user@ravel rmi-prob]$ attempting to bind...
binding succeeded
[user@ravel rmi-prob]$ java jec.ServerTest
looking for server...
found the server.
Result: The time is 18-May-98
------
Bob L.
P.S. I've got RH5.0 running on a Pentium 120MHz, glibc-2.0.7-7.
--
Robert Lynch-Berkeley CA [EMAIL PROTECTED]
http://www.best.com/~rmlynch/
--
John Collins wrote:
>
> Stephen Wynne wrote:
>
> > In message <[EMAIL PROTECTED]>, John Collins writes:
> >
> > However, 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.
> >
> > John,
> >
> > I had no problems registering and running a simple RMI example on
> > 1.1.5v5. If you could send me a small RMI client/server pair that
> > demonstrates your problem, I'd check it out for you on my RH 5.0
> > setup.
> >
> > I hesitate to make any promises because you've clearly done more work
> > on RMI than I have, and you would have tried all the obvious things.
> > However, I do have Java source here and can look at it from that
> > angle.
>
> OK. I'm still stuck. I've attached a tar file that exhibits the problem. It's
> about as simple as an RMI app can be.
>
> The problem:
> When I start up an RMI server, I get the following exception at the point
> where I do the Naming.rebind(name, server); (This is the printout from
> exception.printStackTrace();)
> ---
> java.rmi.ServerException: Server RemoteException; nested exception is:
> java.rmi.AccessException: Registry.rebind
> ---
>
> The environment:
> Red Hat 5.0/Pentium II, jdk1.1.5-v7. I have the same problem both with
> glibc-2.0.7-6 and glibc-2.0.7-7. I'm running the example locally, and it
> doesn't matter whether I'm logged in to the net or not.
>
> The code:
> There's an interface called jec.Server, a server class called jec.ServerImpl,
> and a client class called jec.ServerTest. I've supplied both the sources and
> the .class files. My test on NT involved moving over just the .class files
> from Linux, and that worked, so I deduce the problem is in the Linux runtime.
>
> To run the example.
> - Install the class files in the CLASSPATH, or install them and modify the
> CLASSPATH to see them.
> - Start the rmiregistry
> - In one shell, do java jec.ServerImpl
> - in another shell, do java jec.ServerTest
> The result should be that the line Result: <current date> gets printed out,
> after which the client exits. On Linux this isn't happening.
>
> So, now the question is, did I do something really stupid, or is there
> something wrong with my environment that I'm not seeing, or did I turn over a
> rock that needed looking under? Thanks.
>
> John Collins
> University of Minnesota
> [EMAIL PROTECTED]
>
> ---------------------------------------------------------------
>
> Name: rmi-test.tar
> Part 1.2 Type: Unix Tape Archive (application/x-tar)
> Encoding: base64
