When using combinations of Orbix and OrbixNames on a machine with multiple IP addresses or aliases configured, there may be some instances, when not using the primary IP address, that extra connections are made by Orbix.

This is caused by having inconsistencies between the values of the Orbix C++, Orbix Java and OrbixNames configuration variables. Orbix Java (OrbixWeb) variables are also relevant because OrbixNames is a Java component.

For example:

On a machine with 10.3.88.90 set as the primary IP address with the corresponding hostname host1 and an alias, 10.3.74.79 with a locally defined hostname host2 defined. If you intend to use host2 when connecting via various Orbix components, you must make all of the components aware of this.

This can be done by setting a number of configuration variables in the config files.

For Orbix C++ you first need to set IT_LOCAL_HOST to be the hostname required. This is set in the Orbix scope. You are also recommended to set IT_ENABLE_MULTI_HOMED_SUPPORT="YES".

In the OrbixNames scope you should set the IT_NAMES_SERVER_HOST to be the same hostname.

Set configuration variable IT_LOCAL_HOSTNAME to the hostname, in the orbixweb3.cfg. If this configuration variable is not set the incorrect hostname is put into the IOR, and later on an unexpected connection may be opened.

Therefore, in the example described above, where you wish to use the alias hostname host2, you would set the outlined configuration variables as follows:

  Orbix.IT_LOCAL_HOST="host2";
  Orbix.IT_ENABLE_MULTI_HOMED_SUPPORT="YES";
  OrbixNames.IT_NAMES_SERVER_HOST="host2";
  OrbixWeb.IT_LOCAL_HOSTNAME="host2";