Error Initializing RMI Server

Question

Please look at my question in the RMI forum:
http://forum.java.sun.com/thread.jspa?threadID=639192
Thanks very much.

Answer 1

There are three cases of stub not found:
1. When exporting (or constructing UnicastRemoteObject). This means that the server JVM can't find the stub, it probably doesn't exit.
2. When binding (Naming.bind or Registry.bind). This means that the Registry can't find the stub. This means either (a) you aren't using the codebase feature and the Registry doesn't have the stub in its classpath or (b) you are using the codebase feature and something is wrong with the setup of that: check your codebase server logs: if nothing shows you aren't setting java.rmi.server.codebase at the server; if 404 errors show you don't have the classes where you think you do at the codebase server.
3. When looking up (Naming.lookup or Registry.lookup). This means that the client can't find the stub. Again there are two reasons for this, bearing in mind that you have already got past steps 1 and 2. (a) you aren't using the codebase feature and the stub isnt' on the client's classpath, or (b) you are using the codebase feature and something is wrong, see above. An additional possibility for 3.(b) is overkill: you are using the codebase feature and the stub is on the Registry's classpath. This will cause the Registry to clobber the codebase information so the client doesn't see it.
EJP