[tao-users] Format of corbaloc:uiop

[Phil Mesnier]

Hi Milan,

I haven't had time to go all the way to the root of the problem, but it looks like the problem is not with the CORBALOC parser, which you are using correctly, rather something in the UIOP_* that is returning an object key that improperly includes the '|' separator as part of the object key sequence.

Can you create a bugzilla entry for this bug and someone will address it as soon as possible. If you'd like to fund an increase in priority, that would be great too.

Best regards,
Phil

> On Apr 26, 2016, at 9:06 AM, Milan Cvetkovic <milan.cvetkovic at mpathix.com> wrote:
> 
> The document you are referring to describes how to specify the endpoint for a server, when using -ORBListenEnpoints option.
> 
> I am looking for a way for client to invoke that server using a corbaloc IOR.
> 
> I can access the server using the 'old style:
> uioploc:///tmp/mysock|OBJ_KEY
> but cannot access the server using corbaloc:
> corbaloc:uiop:/tmp/myscock|OBJ_KEY
> 
> I think 'corbaloc:uiop:/tmp/myscock|OBJ_KEY' is a valid IOR, but I am getting OBJECT_NOT_EXIST, as a result of client sending '|OBJ_KEY' as object key.
> 
> Milan.
> 
> Johnny Willemsen wrote:
>> Hi,
>> 
>> See TAO/docs/ORBEndpoint.html
>> 
>> Best regards,
>> 
>> Johnny Willemsen
>> Remedy IT
>> Postbus 81 | 6930 AB Westervoort | The Netherlands
>> http://www.remedy.nl
>> 
>> On 04/26/2016 12:06 AM, Milan Cvetkovic wrote:
>>> Hi TAO,
>>> 
>>> what is the correct format of corbaloc IOR for UIOP?
>>> 
>>> I am trying 'corbaloc:uiop:/tmp/randesvous|OBJ_KEY', but in that case
>>> _narrow() throw OBJECT_NOT_EXIST...
>>> 
>>> 
>>> More details bellow, thanks, Milan.
>>> 
>>>     TAO VERSION: 2.3.3
>>>     ACE VERSION: 6.3.3
>>> 
>>>     HOST MACHINE and OPERATING SYSTEM:
>>>         Linux debian 7
>>> 
>>>     THE $ACE_ROOT/ace/config.h FILE: config-linux.h
>>>     THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE:
>>>         platform_linux.GNU
>>> 
>>>     AREA/CLASS/EXAMPLE AFFECTED: TAO/Strategies/UIOP_Connector.cpp
>>> 
>>>     DOES THE PROBLEM AFFECT:
>>>         EXECUTION? YES
>>> 
>>>     SYNOPSIS:
>>>        Cannot establis client connecttion to a server using
>>>        corbaloc:uiop reference
>>> 
>>>     DESCRIPTION:
>>> 
>>> I run a server, which 'listens' on UIOP socket, for example, using
>>> -ORBListenEndpoints uiop:///tmp/endpoint
>>> 
>>> The client uses the following snippet to invoke a function on server:
>>> 
>>> CORBA::ORB_var orb = CORBA::ORB_init (argc, argv);
>>> CORBA::Object_var o = orb->string_to_obj (str);
>>> CORBA::MyObj_var myo = MyObj::_narrow(o);
>>> myo->invoke ();
>>> 
>>> 
>>> When using uioploc:///tmp/endpoint|OBJ_KEY, MyObj::invoke() is properly
>>> invoked.
>>> 
>>> If I try to use 'corbaloc:uiop:/tmp/endpoint|OBJ_KEY', _narrow() above
>>> throws 'OBJECT_NOT_EXIST'. Tracing with -ORBDebugLevel 10 reveals that
>>> instead of object key 'OBJ_KEY' client is looking for '|OBJ_KEY'.
>>> _______________________________________________
>>> tao-users mailing list
>>> tao-users at list.isis.vanderbilt.edu
>>> http://list.isis.vanderbilt.edu/cgi-bin/mailman/listinfo/tao-users
> 
> _______________________________________________
> tao-users mailing list
> tao-users at list.isis.vanderbilt.edu
> http://list.isis.vanderbilt.edu/cgi-bin/mailman/listinfo/tao-users

--
Phil Mesnier
Principal Engineer & Partner

OCI | WE ARE SOFTWARE ENGINEERS.
tel  +1.314.579.0066 x225
ociweb.com