[omniORB] OmniNames on omniORB 3 pre

[David Riddoch]

Hi,


I've tracked down and fixed the problem with the bootstrap agent in
omniORB 3.  There was a deadlock if you used the ORBInitialHost
ORBInitialPort mechanism for getting initial references.

The fix wil be in CVS tonight ...


David


On Thu, 2 Dec 1999, David Riddoch wrote:

> I've had a look at this, and yes there is a problem.  In theory it should
> have all worked as it used to.  It does work in the case where you put
> NAMESERVER IOR:... into the config file, but not when you use
> ORBInitialHost and ORBInitialPort.  Looks like I've done something to
> damage the bootstrap agent.
> 
> I'll look into it.
> 
> Cheers,
> David
> 
> 
> On Tue, 30 Nov 1999, Kapla, Jami wrote:
> 
> > Hello David,
> > 	We are trying to use the Omniidl3 on linux 6.0
> > and test the echo example. The eg1 works however the eg3_impl
> > fails when the call to orb->resolve_initial_references("NameServece")
> > is called. We are trying to find what exception is being thrown. However
> > I believe it has something to do with either the ORB is configured wrong
> > or the omniORB.cfg file is not configured correctly. There is a mention 
> > in the 3.0 release notes of changes to the log file for omniNames but no
> > specifics.  currently we start the omniNames:
> > 
> > omniNames -start 1234
> > which then seems to start it ok.
> > 
> > omniORB.cfg has:
> > ORBInitialHost korea (my machine)
> > ORBInitialPort 1234
> > 
> > and OMNIORB_CONFIG is set in the environment to the correct path.
> > 
> > However we are using the documentation for OmniOrb2, so maybe this has 
> > changed some(?).
> > We simply did a make all and ran eg3.impl but the resolve_initial_refernces
> > call fails. (it also fails for all ID's except "RootPOA").