When realizing a Remote Java Application, the remote execution server (of the "parent") must be listening on a "routable" (public) address so that the Remote Java Application can connect back to it.
On servers with multiple network adapters, it's possible that the remote execution server will use a non-routable (private) address and thus the Remote Java Application may not be able to connect back to the "parent".
When realizing a Remote Java Application, the remote execution server (of the "parent") must be listening on a "routable" (public) address so that the Remote Java Application can connect back to it.
On servers with multiple network adapters, it's possible that the remote execution server will use a non-routable (private) address and thus the Remote Java Application may not be able to connect back to the "parent".