ObjID Already in Use

VERSION 3 Published

Created on: 14-Dec-2006 13:19 by flux - Last Modified:  26-Feb-2008 16:11 by Guest

Stack trace:

Caused by: java.rmi.server.ExportException: internal error: ObjID already
in use at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:168)
at sun.rmi.transport.Transport.exportObject(Transport.java:69)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:190)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145)
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:78)


In your configuration, there are two RMI registries created in the same JVM. You cannot have two RMI registries in the same JVM due to an RMI restriction. You can refer to the following FAQ link: http://jguru.com/faq/view.jsp?EID=741019

You can accomplish your requirement using a single RMI registry. Each engine will use the same RMI registry, with different bind names. This can be configured using the SERVER_NAME configuration parameter.

For example, in the first configuration:

server_name=engine1
registry_port=1099


In this second configuration:

server_name=engine2
registry_port=1099
Average User Rating
(0 ratings)




There are no comments on this document