rmi AccessException problem

[Stevoie]

Please help.
I've got a AccessException being thrown when i attempt to bind to a rmi registry running on a remote machine. I've given full permissions to both the server and client grant {
permission java.security.AllPermission;
};

but it still throwns the exception. Run the server using
java -Djava.security.policy==policy.file Server
Client is the same command.

Anyone any ideas?
Thanx

StevoIE

 

[Stevoie]

the exception thrown is:


java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.AccessException: Registry.Registry.bind disallowed; origin /10.37.2.83 is non-local host


The client attempts to bind an object to the rmiregistry on a remote machine and the above error is given back

StevoIE

 

[nasiraliadil]

hi
i got stuck with the java.rmi.unmarshalException when calling my bean from the client program.i want to know what is the reason when this exception occurs and how to handle it.

 

[sedj]

StevoIE :
I don't believe it is possible to bind to a remote registry - RMI servers must bind on a local registry. The _Skeleton then listens on a certain port (3578 or something like that). The distributed _Stub then connects to the specified IP, on the port - which allows you to perform distributed invokation of remote objects.

You shouldn't need to bind a client anyway - thats the idea of remote servers and their client _Stubs ....


nasiraliadil :

The UnmarshalException is caused by many, many different reasons, and without a stack trace I cannot tell you which it is. Though possible causes are :
- Jar files and class files on your CLASSPATH are conflicting.
- Native method dll's or so's are not available, or your LD_LIBRARY_PATH is incorrect.
- Your resources (beans etc) are not in scope of your rmi server, or are not configured properly.

Basically the exception means that when the rmi server was attempting to "marshal" or prepare your objects for calls, it ran into some config problem. Check your docuimentation, classes and system dependencies.