I think you're hitting one of the problems with RMI on multi-homed machines,
the stubs hold a liveref object which contains an address and a port. On a
machine with multiple addresses you sometimes endup shipping a stub that
contains an address on the "wrong" interface. Take for example my setup
w
[EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: RMI Problems
Forwarded by: [EMAIL PROTECTED]
> Sounds like you're exporting an RMI URL with //localhost (127.0.0.1) from
> one machine. If you're constructing the RMI URL by invoking the InetAddress
> get
Sounds like you're exporting an RMI URL with //localhost (127.0.0.1) from
one machine. If you're constructing the RMI URL by invoking the InetAddress
getLocalHost() method, that may be returning the loop-back interface
address. I thought this problem was solved with the latest JDK, but
you can w
[EMAIL PROTECTED] wrote:
> I have been attempting to get an RMI Client and Server to run using
> 2 Linux boxes running Red Had 6.1 (one dual boots 95). The Client
> and Server are "textbook" examples.
>
> I have run them succesuffly on Win95, WinNT and Solaris
> networks. When I run both on the
I have been attempting to get an RMI Client and Server to run using
2 Linux boxes running Red Had 6.1 (one dual boots 95). The Client
and Server are "textbook" examples.
I have run them succesuffly on Win95, WinNT and Solaris
networks. When I run both on the same linux machine, it works. In
Hi
I have a problem with rmi.
I use Linux RedHeat 5.0 and jdk-1_1_6sn-1_1glibc_i386.
When I start my server application this is the output :
java.rmi.UnexpectedException: Unexpected exception; nested exception is:
java.lang.ClassNotFoundException: MyServerImpl_Stub
but the class is ther
