Fwd: problem accessing a TAO-based CORBA server on a multihomed setup using omniORB

I've been trying to access a TAO-based CORBA server which is on a
multihomed machine. The name service is omniNames and the client is
OmniORB-based.

The multihomed machine is a VM running Windows. It has an interface
(10.0.2.0/24) that connects to the internet through a NAT and a
connection-to-host (2.0.10.0/24). I've added the following
clientTransportRule:

clientTransportRule = 10.0.2.0/255.255.255.0    none
                   = *                          tcp

Connecting fails with a NoUsableProfile error. The decoded IOR gives

1. IIOP 1.2 10.0.2.15 51961 "....RSTX..Y.M.............."
           TAG_ORB_TYPE 0x54414f00
           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:


2. IIOP 1.2 2.0.10.2 51961 "....RSTX..Y.M.............."
           TAG_ORB_TYPE 0x54414f00
           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:

I've debugged it in the omniorb source code, and it seems that omniorb
restricts itself to the first IIOP profile it finds (which would
explain the problem).

My questions:
 - is the omniORB behavior intentional ? Is ill-defined in the
standard / an omniORB bug / a TAO bug / none of the above ?
 - do you know if I have a way to make it work ?

Thanks
Sylvain

_______________________________________________
omniORB-list mailing list
[email protected]
http://www.omniorb-support.com/mailman/listinfo/omniorb-list