Issue 3360: INS Issue: Orderof how  the Initial reference is resolved (naming_ftf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary:  The latest INS doc 99-12-03.pdf explains the order the Initial reference 
 should be resolved is
 1. Try using -ORBInitDef definition
 2. Try using -ORBDefaultInitDef defintion
 3. Then finally try with Pre-Configured ORB Settings.
 
 The above would be the resolve_initial_references protocol. Now, If the user
 sets a -ORBInitDef in the format
 
 -ORBInitDef NotificationService=corbaloc:rir:/NotificationService 
 
 If the user does orb.resolve_initial_references( "NotificationService" )
 then according to the spec, r_i_r() first checks -ORBInitDef's, In this case 
 finds one and also finds that the NotificationService can be obtained by
 r_i_r() 
 again it calls the same method. Doesn't this lead to an infinite loop ?
Resolution: 
Revised Text: 
Actions taken:
February 24, 2000: received issue
Discussion: 

End of Annotations:=====
ate: Thu, 24 Feb 2000 17:12:52 -0800 (PST)
From: Hemanth Puttaswamy <Hemanth.Puttaswamy@eng.sun.com>
Reply-To: Hemanth Puttaswamy <Hemanth.Puttaswamy@eng.sun.com>
Subject: INS issue
To: issues@omg.org
Cc: rip-dev@eng.sun.com
MIME-Version: 1.0
Content-MD5: 9iiI2IaOcN+xpSQIWxSFPg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.2 SunOS 5.7 sun4u sparc 
Content-Type: TEXT/plain; charset=us-ascii
X-UIDL: \o<!!QSe!!5F~!!b_O!!

Hi,
 
My name is Hemanth working at Sun Microsystems (Javasoft's CORBA
technology 
group). The latest INS doc 99-12-03.pdf explains the order the Initial
reference 
 should be resolved is
 1. Try using -ORBInitDef definition
 2. Try using -ORBDefaultInitDef defintion
 3. Then finally try with Pre-Configured ORB Settings.
 
 The above would be the resolve_initial_references protocol. Now, If
the user
 sets a -ORBInitDef in the format
 
 -ORBInitDef NotificationService=corbaloc:rir:/NotificationService 
 
 If the user does orb.resolve_initial_references(
"NotificationService" )
 then according to the spec, r_i_r() first checks -ORBInitDef's, In
this case 
 finds one and also finds that the NotificationService can be obtained
by
 r_i_r() 
 again it calls the same method. Doesn't this lead to an infinite loop
?

Thx,
Hemanth Puttaswamy
CORBA technology team

Attached.

Attachment Converted: "c:\program files\qualcomm\eudora
mail\attach\CClientsOMGPartner ReportsMar 2000 OMG Partner Report.doc"
Issue 3360 describes a problem with -ORBInitRef with a corbaloc:rir:
string. That issue involves directly specifying a cycle. This issue
involves a more subtle cycle, which I believe is more likely to catch
people out.

Suppose the user has administratively configured their ORB with a
naming service reference. Now they specify a command line of

  -ORBDefaultInitRef corbaname:rir:#Services

Now an attempt to resolve any initial reference will result in a
cycle. A call to

  resolve_initial_references("foo")

will turn into

  string_to_object("corbaname:rir:#Services/foo")

the first phase of which will turn into

  resolve_initial_references("NameService")

which ought to find the administratively configured object reference,
but section 4.8.4.1 (in ptc/99-12-03) says that if there is an
-ORBDefaultInitRef, that must be tried in preference. The ORB thus
loops for ever.

Section 4.8.4.2 should be modified to permit the ORB to ignore
-ORBDefaultInitRef when r_i_r() is recursively called.


Cheers,

Duncan.

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