Java.Rmi.Serverexception: Remoteexception Occurred in Server Thread (Classnotfoundexception)

java.rmi.ServerException: RemoteException occurred in server thread (ClassNotFoundException)

There are four cases of this exception.

1. When exporting: you didn't run 'rmic' and you didn't take the steps described in the preamble to the Javadoc for UnicastRemoteObject to make it unnecessary.

2. When binding: the Registry doesn't have the stub or the remote interface or something they depend on on its classpath.

3. when looking up: the client does't have these things on its classpath.

4. When calling a remote method: you either sent something to the server of a class not present on its CLASSPATH, or received something from the server (including an exception) of a class not on your CLASSPATH: in both cases possibly a derived class or interface implementation of a class or interface mentioned in the remote interface's method signature.

This is case 2. The Registry can't find the named class.

There are several solutions:

1. Start the Registry with a CLASSPATH that includes the relevant JARs or directories.

2. Start the Registry in your server JVM, via LocateRegistry.createRegistry().

3. Use dynamic stubs, as described in the preamble to the Javadoc of UnicastRemoteObject. However you may then still run into the same problem with the remote interface itself or a class that it depends on, in which case 1-3 above still apply to that class/those classes.

4. Ensure that case (4) above doesn't occur.

5. Use the codebase feature. This is really a deployment option and IMO something to be avoided at the initial development stage.

Why java.rmi.ServerException: RemoteException occurred in server thread shows?

If you look at the entire stack trace, which you should have posted in your question, you will probably find that the error occurred in bind() or rebind(). That indicates that the Registry doesn't have the class mentioned on its CLASSPATH.

Solution: either run the Regsistry with an appropriate CLASSPATH, or run it inside the server JVM via LocateRegistry.createRegistry().

java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:

Try start the rmiregistry in the command line with the same path you run javac and java.

Java RMI, cant find stub class , java.rmi.ServerException: RemoteException occurred in server thread;

The RMI Registry can't find that class. So there is some difference in your laptop's setup concerning the Registry.

RMI, ServerException: RemoteException

When you start your server application you have to point where RMI should look for classes
you can do it using java.rmi.server.codebase property, so the right command looks like this:

java -classpath "D:\[...]\bin" 
-Djava.rmi.server.codebase=file:/D:\[...]\bin/ example.hello.Server

---

Related Topics