-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
P4
-
None
-
Affects Version/s: 1.4.0
-
Component/s: other-libs
-
generic
-
generic
The TAO 1.1.19 Naming_Service has a quirk that it will put "localhost" in its
IORs if that's what you specify as an end point.
If, on a second machine, you do a string_to_object on a corbaloc for the
TAO Naming_Service and then try to narrow it, your program will go into
an infinite loop.
Hemanth and I are assuming that we have code in place to try to fall back
on the original IOR -- the corbaloc URL. The LocateRequest is successful,
and we try to invoke on the resulting IOR which says "localhost" even though
it isn't. This would probably occur if a service returned any bad IOR.
Please see comments section for location of current TAO build
IORs if that's what you specify as an end point.
If, on a second machine, you do a string_to_object on a corbaloc for the
TAO Naming_Service and then try to narrow it, your program will go into
an infinite loop.
Hemanth and I are assuming that we have code in place to try to fall back
on the original IOR -- the corbaloc URL. The LocateRequest is successful,
and we try to invoke on the resulting IOR which says "localhost" even though
it isn't. This would probably occur if a service returned any bad IOR.
Please see comments section for location of current TAO build