[omniORB] Problem with omniORB client + Orbix Web server

[Duncan Grisby]

On Monday 24 November, "Romans Krjukovs" wrote:

> When ORB is configured to use omniORB Name Service - this code works fine.
> If i reconfigure to use Orbix Name Service (in registry NameService=corbaname::LETTO:1570) - my code fails.
> with Error message:
> 
> Traceback (most recent call last):
>   File "C:\omniCX2\NS_server.py", line 13, in ?
>     rootContext = obj._narrow(CosNaming.NamingContext)
>   File "C:\omniORB\lib\python\omniORB\CORBA.py", line 650, in _narrow
>     return _omnipy.narrow(self, dest._NP_RepositoryId)
> omniORB.CORBA.TRANSIENT: Minor: TRANSIENT_NoUsableProfile, COMPLETED_NO.
> 
> So, it is about profile. And it is not usable.

Since you are using a corbaname URI, the original object reference you
are using must have a usable IIOP profile -- the one constructed from
the URI. The problem must be that the thing listening on port 1570 is
the Orbix daemon, which forwards omniORB to a different object. It is
that forwarded object reference that has no usable profile. Try
running your code with -ORBtraceLevel 25, and I expect you will see
messages about location forwarding before the TRANSIENT exception.

The root of the problem may be that OrbixWeb doesn't support the
interoperable naming service, so it does the wrong thing when omniORB
tries to contact the object with key "NameService".

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --