[omniORB] resolve_initial_references hangs

[Mark Zimmerman]

Unfortunately, I have not been able to reproduce the problem. The last
time that it occurred, though, I attached to one of the affected
processes and found it to be blocked at the call to
resolve_initial_references ("NameService"), but I didn't capture the
results of a 'where', which might have shown the block point at a
lower level. 

If it happens again I will try to get more information; since the
programs are still in a constant state of development it may pop up
again.

-- Mark

On Tue, Apr 17, 2001 at 10:07:07AM +0100, Duncan Grisby wrote:
> On Monday 16 April, Mark Zimmerman wrote:
> 
> > We have an application in which a shell script starts many instances
> > of a program in parallel. When the number of instances is 'too large'
> > (meaning some number that is greater than eight but less than 32 -
> > I've not narrowed it down) many of the programs get stuck at the
> > resolve_initial_references ("NameService") call and never unblock,
> > even long after the successful instances terminate.
> 
> Strange. How are you configuring your initial references?  Try running
> the clients with arguments -ORBtraceLevel 10 -ORBtraceInvocations.
> That might show what's going on. Alternatively, it might change the
> timing so the problem doesn't occur any more...
> 
> Another thing to try is to attach to the frozen process with a
> debugger, and see where it is blocked.
> 
> Cheers,
> 
> Duncan.
> 
> -- 
>  -- Duncan Grisby  \  Research Engineer  --
>   -- AT&T Laboratories Cambridge          --
>    -- http://www.uk.research.att.com/~dpg1 --