[omniORB] Multi-profile IOR

[Tatiana Lazareva]

2011/9/28 Tatiana Lazareva <tatiana.alexandrovna.lazareva at gmail.com>

> Evgeni,
> Yes, my client get TRANSIENT exception in multi-profile IOR case.
> For example, when I use single IOR:
> /omcvobs/simbsso3g/external/omniORB/solaris/build/bin/catior
> IOR:000000000000002b49444c3a6f6d672e6f72672f436f734e616d696e672f4e616d696e67436f6e746578744578743a312e30000000000001000000000000007c0001020000000019666538303a3a3230333a626166663a666535373a3565396400000af90000000b4e616d6553657276696365000000000300000000000000080000000041545400000000010000001c0000000000010001000000010501000100010109000000010001010941545403000000084e8313b0a8090001
> Type ID: "IDL:omg.org/CosNaming/NamingContextExt:1.0"
> Profiles:
> 1. IIOP 1.2 fe80::203:baff:fe57:5e9d 2809 "NameService"
>             TAG_ORB_TYPE omniORB
>             TAG_CODE_SETS char native code set: ISO-8859-1
>                           char conversion code set: UTF-8
>                           wchar native code set: UTF-16
>                           wchar conversion code set: UTF-16
>
>             TAG_OMNIORB_PERSISTENT_ID 4e8313b0a8090001
>
> the registration is successfully performed, but if I use dual IOR:
> /omcvobs/simbsso3g/external/omniORB/solaris/build/bin/catior
> IOR:000000000000002B49444C3A6F6D672E6F72672F436F734E616D696E672F4E616D696E67436F6E746578744578743A312E3000000000000200000000000000A400010200000000103139322E3136382E3230372E313100003A9800000000001F5374616E646172644E532F4E616D655365727665722D504F412F5F726F6F7400000000030000000000000008000000004A414300000000010000002000000000000100010000000105010001000101090000000205010001000101000000000100000020000000000001000100000001050100010001010900000002050100010001010000000000000000B80001020000000024666538303A3030303A303030303A30303A3230333A626166663A666535373A35653964003A9800000000001F5374616E646172644E532F4E616D655365727665722D504F412F5F726F6F7400000000030000000000000008000000004A4143000000000100000020000000000001000100000001050100010001010900000002050100010001010000000001000000200000000000010001000000010501000100010109000000020501000100010100
> Type ID: "IDL:omg.org/CosNaming/NamingContextExt:1.0"
> Profiles:
> 1. IIOP 1.2 192.168.207.11 15000 "StandardNS/NameServer-POA/_root"
>             TAG_ORB_TYPE 0x4a414300
>             TAG_CODE_SETS char native code set: ISO-8859-1
>                           char conversion code set: UTF-8
>                           wchar native code set: UTF-16
>                           wchar conversion code set: 0x05010001, 0x00010100
>
>             TAG_CODE_SETS char native code set: ISO-8859-1
>                           char conversion code set: UTF-8
>                           wchar native code set: UTF-16
>                           wchar conversion code set: 0x05010001, 0x00010100
>
>
> 2. IIOP 1.2 fe80:000:0000:00:203:baff:fe57:5e9d 15000
> "StandardNS/NameServer-POA/_root"
>             TAG_ORB_TYPE 0x4a414300
>             TAG_CODE_SETS char native code set: ISO-8859-1
>                           char conversion code set: UTF-8
>                           wchar native code set: UTF-16
>                           wchar conversion code set: 0x05010001, 0x00010100
>
>             TAG_CODE_SETS char native code set: ISO-8859-1
>                           char conversion code set: UTF-8
>                           wchar native code set: UTF-16
>                           wchar conversion code set: 0x05010001, 0x00010100
>
> the registration fails due to TRANSIENT exception.
> I use the *[TL]*same ORB in both case. *[TL]*And I am sure that the
> problem with  my client but I cannot understand the reasons.Could you
> please explain what are the reasons possible?
>

>
2011/9/28 <evgeni.rojkov at durr.com>
>
> **
>>
>>  Hi Tania,
>> it's no difference registering IORs by the NameService if single- or
>> multi-profile.
>> Does your client get TRANSIENT exception?
>> Do you use different ORB for client?
>> For example javaIDL (java 2 version) doesn't handle client calls to
>> servants located using multi-profiles IORs correctly.
>> Could it be your problem?
>> Regards, Evgeni
>>
>>
>>  ------------------------------
>>  *Von:* omniorb-list-bounces at omniorb-support.com [mailto:
>> omniorb-list-bounces at omniorb-support.com] *Im Auftrag von *Tatiana
>> Lazareva
>> *Gesendet:* Mittwoch, 28. September 2011 13:52
>> *An:* omniorb-list at omniorb-support.com
>> *Betreff:* [omniORB] Multi-profile IOR
>>
>> Hi all,
>> I have a question about multi-profile IOR. I use the following
>> CORBA: omniORB-4.1.4.tar.gz under Solaris 10.
>> When I try register servants using the multiple-profile IOR I got an
>> exception: TRANSIENT. Does my CORBA support registration with
>> multiple-profile IOR? If yes, can you explain how should I perform
>> servant registration using the multiple IOR?
>>
>> --
>>
>> Cheers,
>>
>> *T*atiana *L*azareva**
>>
>> e-mail (regular): *Tatiana.Alexandrovna.Lazareva at gmail.com*
>>
>> e-mail (office): *yumanova at mera.ru*
>>
>>
>
>
> --
>
> Cheers,
>
> *T*atiana *L*azareva**
>
> e-mail (regular): *Tatiana.Alexandrovna.Lazareva at gmail.com*
>
> e-mail (office): *yumanova at mera.ru*
>
>


-- 

Cheers,

*T*atiana *L*azareva**

e-mail (regular): *Tatiana.Alexandrovna.Lazareva at gmail.com*

e-mail (office): *yumanova at mera.ru*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20110928/9f41658f/attachment.htm