[omniORB] Changing endPoint with options of ORB_init

Duncan Grisby duncan at grisby.org
Fri Mar 12 17:29:55 GMT 2004


On Friday 12 March, Thomas Baron wrote:

> When the ORB_init fails, I destroy the ORB (even sleep()ing for a few
> seconds after the call) and I try another port (incrementing port
> number) with the option 'endPoint' in the parameter 'const char
> *options[][2]'
> But the next ORB_init still fails, with an error message saying it can
> bind to the port number I specified first.

There was a bug with this that was fixed in 4.0.3. What version are
you using?  Please upgrade to 4.0.3 if you're not already using it. If
you are using 4.0.3, please run with -ORBtraceLevel 25 and post the
logs.

Cheers,

Duncan.

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



More information about the omniORB-list mailing list