[omniORB] Naming Service IP Address

[Duncan Grisby]

On Wed, 2010-02-03 at 15:26 -0800, Piccoli, Joseph wrote:

> I am having a problem creating a NamingContext on Solaris. I create an
> initial context with the IP address of the machine running the
> omniNames server, which is not running on the same machine that my
> omniorb server is running. This works correctly. Next, I try to add a
> context to the initial context using bind_new_context( ). The response
> to this contains an IP address which is different from the one
> associated with the initial context. I do not know if this an
> omniNames or omniorb issue. Is there a means to force omniNames to
> always use the same IP address in establishing contexts? I have
> attempted various settings of the “endPontNoPublish”,
> “endPointNoListen”, “clientTransportRule”, and “serverTransportRule”
> settings without success.

endPointPublish is the option you want:

http://omniorb.sourceforge.net/omni41/omniORB/omniORB008.html#htoc105

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --