[omniORB] problem with circularly federated OB Naming and OmniNames ...

[Duncan Grisby]

On Tuesday 7 March, Philip Lijnzaad wrote:

[...circular links between name services...]

> Such a circular path can be used in e.g. a context.resolve() call, but when
> the length becomes deeper than say 4 hops, my clients (Mico's nsadmin and
> Omni's nameclt ... yes, I'm being very eclectic here) get stuck: it suddenly
> takes 20 secs to resolve, and it seems to lasts exponentially longer with
> increasing length of the futile this/that/this/that links.

I imagine that this is an interaction between the threading models of
omniORB and ORBacus. Each nested call is re-entering the ORBs'
dispatch routines. Unless it is actually causing a problem for you, I
wouldn't worry about it.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --