RMI uses incorrect InetAddress on machine with two nics

Question

Hello All,
RMI registry and server run on the same host. Host has two nics, one assigned for private network (192.168.x.x) and another for global.
For the sake of creating RMI registry I use the global one and specify it as four dot-delimited numbers instead of machine name:
Registry registry = LocateRegistry.getRegistry("xxx.xxx.xxx.xxx", rmiPort); // "xxx.xxx.xxx.xxx" is global IP addressInvoking a method with just a port as a single parameter causes RMI to bind to the private address, so I avoided that trouble by using numeric IP.
Remote client is able to locate the registry and extract the stub from it now, but ironically retrieved stub contains private address inside.
Debugger shows that the proxy stub contains TCPEndpoint which resolves to 192.168.xxx.xxx:yyyy
I am exporting the object on the server side by using UnicastRemoteObject.exportObject(myObj, 0) method.
Unfortunately, there is no method which would allow to specify the InetAddress to bind the object on.
I've seen the battle on page [Remote Method Invocation (RMI) - Why does RMI server sets its connection address?|http://forums.sun.com/thread.jspa?threadID=5366985].
Close questions are discussed, but I haven't found answer on my question.
Is there an ability to specify the address when exporting the object?
Or any workaround to let the client retrieve the proper stub which can be used to send requests to the server?
Thank,
Alex.

Answer 1

For the sake of creating RMI registry I use the global one and specify it as four dot-delimited numbers instead of machine name:
Registry registry = LocateRegistry.getRegistry("xxx.xxx.xxx.xxx", rmiPort); // "xxx.xxx.xxx.xxx" is global IP address
That doesn't create a registry. It just returns a stub to an existing registry.
Invoking a method with just a port as a single parameter causes RMI to bind to the private address.No it doesn't. It causes RMI to construct a stub using "localhost" as the hostname. If this maps to the private address via your /etc/hosts file or DNS, so be it.
Remote client is able to locate the registry and extract the stub from it now, but ironically retrieved stub contains private address inside.Nothing ironic about it. The stub doesn't know where you got it from. The address inside the stub is controlled by what "localhost" resolves to in the server JVM. If it resolves to something inconvenient, either change that or set the system property java.rmi.server.hostname to the desired IP address or hostname in the server JVM.
Unfortunately, there is no method which would allow to specify the InetAddress to bind the object on.You don't normally need one, see above, although in pathological cases you could use an RMIServerSocketFactory, which does give you that ability.
I haven't found answer on my question.See also the RMI FAQ, item A.1.
Is there an ability to specify the address when exporting the object? See above.