[omniORB] Problem with multiple-profile IOR's

Joe Bronkema joseph.d.bronkema at lmco.com
Thu Oct 2 09:17:35 BST 2003


I'm using omniORBpy 2.2 on Solaris 8, and have run into a problem where 
an omniORBpy client program fails to connect to a server that issues a 
multiple profile IOR.

The network uses hosts files, with no DNS.
The server is on host_a, which has two network interfaces with hostnames 
of host_a and host_aprime.
The IOR uses host_aprime in the first profile and host_a in the second 
profile.

The client is on host_b, which has host_a but not host_aprime in its 
hosts file.
When the client first attempts to invoke a method on the server object, 
it gets a TRANSIENT connect failed.
I tried setting clientTransportRule to use the IP address of host_a, but 
then I got a TRANSIENT no usable profile.

I've not dug into the source code to verify this, but the symptoms 
suggest that once the omniORB client fails at looking up host_aprime, it 
does not go on to try the other profile.

Is there another explanation I'm missing?  The ORB should try the second 
profile if it cannot use the first, right?

Thanks in advance,
Joe Bronkema





More information about the omniORB-list mailing list