[omniORB] Why would resolve_initial_references() be throwing InvalidName

Mark Johnson mark.johnson@onfiber.com
Thu, 28 Mar 2002 16:09:36 -0600


ENV: Red Hat 7.1 (kernel 2.4.7-10), g++ 2.96, omniORB3.0

We have the same code compiled for Solaris, Mandrake, and Red Hat.  The
nameserver is running on the solaris machine.  The instances running on
Solaris and Mandrake run fine, but when the instance is started on the Red
Hat machine, it throws and InvalidName exception.

All the applications are all started with the following command line:

	./ctrlr -ORBInitRef AUST-1=corbaname::neutron -ORBtraceLevel 20

The app on Red Hat says that AUST-1 is not a valid name in the call to
resolve_initial_references().  I can't figure out what would be the problem
here.  Is there anything that I can double check to determine why this would
be happening.

Here's is the trace from omniorb:

omniORB: strand Ripper: start.
omniORB: scavenger : start.
omniORB: gateKeeper is tcpwrapGK 1.0 - based on tcp_wrappers_7.6 
omniORB: Initialising omniDynamic library.
omniORB: Initialising incoming rope factories.
omniORB: strand Rope::incrRefCount: old value = 0
omniORB: Starting incoming rope factories.
omniORB: tcpSocketMTfactory Rendezvouser: start.
omniORB: tcpSocketMTfactory Rendezvouser: block on accept()
omniORB: Activating: root<0>
omniORB: Creating ref to local: root<0>
 target id      : IDL:Controller:1.0
 most derived id: IDL:Controller:1.0
omniORB: createObjRef -- reusing reference from local ref list.
ctrlr: trying to bind to: AUST-1
omniORB: resolve_initial_references throws CORBA::ORB::InvalidName
ctrlr: caught InvalidName exception on resolve_initial_references("AUST-1")
omniORB: scavenger : scanning connections