[omniORB] OmniNames

[Duncan Grisby]

On Friday 2 November, "Olivier Thiboutot" wrote:

> In OmniNames 2.8, if we add -BOAiiop_name_port 127.0.0.1 and -start
> option, no problem at creation. (Self laptop contain application)
> 
> If after we restart with -BOAiiop_name_port 127.0.0.1 still no
> problem...
> 
> If we register a CONTEXT and an Object, we have no problem...
> 
> If we stop OmniNames.exe and restart it with -BOAiiop_name_port
> 127.0.0.1, we crash with internal error closing TCP/IP port number -1!!!
> (No start parameter to reload history)
> 
> If we are not too late, I would appreciate a possible explication and if
> it can affect other process then OmniNames?

Sorry, omniORB 2.8 is such ancient history that I don't think anyone
will be able to help you. I expect it's something to do with the
endpoint settings in the IORs stored in the omniNames log, but I don't
know for certain.

Duncan.

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