[omniORB] Strange omniORB domain socket behavior

John Kamenik jkamenik at patton.com
Mon Oct 2 18:56:24 BST 2006


I am using omniORB 4.0.7 and have found that Unix Domain sockets are  
tied to the hostname and if you change the hostname the IOR no longer  
works because it cannot get a usable profile with the new hostname.   
Is there a way to get omniORB to assume "localhost" if a unix socket  
is used, instead of looking up hostname?

Simple Example (Note: programs were in Python):

oldname $ ./echo_server -f /tmp/echo.ior
oldname $ ./echo_client -f /tmp/echo.ior "testing"
testing
oldname $ hostname newname
newname $ ./echo_client -f /tmp/echo.ior "test again"
CORBA.TRANSIENT(omniORB.TRANSIENT_NoUsableProfile,CORBA.COMPLETED_NO)


The following is my omniORB config file:

endPointPublishAllIFs= 1
endPoint             = giop:unix:
serverTransportRule  = localhost unix
clientTransportRule  = * unix


I have limited the CORBA objects to only use unix sockets because  
both the computer's IP address and hostname could change.


John T. Kamenik (Software Eng.)
jkamenik at patton.com
(301) 975 - 1000 (ext. 168)
Patton Electronics Co.
7622 Rickenbacker Dr.
Gaithersburg, Md 20879





More information about the omniORB-list mailing list