Skip to end of metadata
Go to start of metadata
- When restarting the RMI registry, it is a good idea to take the opportunity to "clean" and re-compile all of the Java classes. It seems like classes the RMI registry is using don't always get recompiled completely.
- If you're trying to start an RMI server, and it complains about "Class not found" for a class that really exists, the RMI registry is in a corrupted state and must be restarted (presubably because of previous problems in loading the same RMI server).
- Make sure the RMI registry is being started with an empty classpath, and the RMI servers are started with a valid java.rmi.server.codebase. While it is technically possible to start the RMI registry with a real classpath, and this will make certain problems go away, it makes everything more complicated in the long run, because it can cover up problems with the codebase property. It is ok for the codebase property to point to a file: URL if you're not going to have the client download copies of the stub files.
- The java.policy file that is in effect when the RMI registry starts will govern all RMI classes that attach to this registry.