[omniORB] Multi-profile IOR

[Duncan Grisby]

On Wed, 2011-09-28 at 17:24 +0400, Tatiana Lazareva wrote:

> 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

I'm rather surprised by this -- that's a link-local IPv6 address, which
won't work in most circumstances, and omniORB should not have published
it in its IOR. How did you configure omniNames?


> 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

This is a JacORB naming service.

[...]
> 2. IIOP 1.2 fe80:000:0000:00:203:baff:fe57:5e9d 15000
> "StandardNS/NameServer-POA/_root"

It has two IIOP profiles in it, which is not the correct way to
represent multiple IP addresses -- they should be in a single IIOP
profile with a TAG_ALTERNATE_IIOP_ADDRESS entry. That may or may not be
the problem.

Please get a trace from your client with -ORBtraceLevel 25. That will
show what's going on.

Cheers,

Duncan.

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