[omniORB] RE: Operating within a vserver

[Russell Kliese]

Thank you for your suggestion, Wernke.

I have tried setting the endPoint option to "endPoint = 
giop:tcp:192.168.6.14:". This causes the following additional lines in 
netstat:

tcp        0      0 192.168.6.14:32852      192.168.6.14:32849      
TIME_WAIT
tcp        0      0 127.0.0.1:32850         192.168.6.14:2809       
TIME_WAIT

But the server still fails to start. Apparently the corba server is 
attempting to connect from the localhost interface to the omniNames, 
however, this won't work in a vserver because the localhost interface is 
not able to be used.

 From my understanding, the endPoint options are used to set up the 
addresses that the CORBA server will listen on, however, I think the 
problem is with the CORBA server trying to contact omniNames.

Is it possible to choose a different address to 127.0.0.1 that the CORBA 
server will bind to when contacting omniNames?

Russell

>Hi,
>
>you should use the endPoint option for your server. See chapter 8.6 of the
>manual for details.
>
>Wernke
>  
>
>>I am having a problem running an omniORB4 corba server from within a 
>>vserver.
>>
>>The IP address assigned to the current vserver is 192.168.6.14, while 
>>the host machine ip addresses are 192.168.6.12 and 127.0.0.1.
>>
>>omninames looks to be running correctly (netstat -an has it 
>>showing as 
>>follows:)
>>
>>tcp        0      0 192.168.6.14:2809       0.0.0.0:*               
>>LISTEN    
>>
>>I have set OMNIORB_USEHOSTNAME=192.168.6.14
>>When I try to run a corba server, I get the following exception being 
>>thrown:
>>throw giopStream::CommFailure from 
>>giopStream.cc:1076(0,NO,TRANSIENT_ConnectFailed)
>>
>>And netstat has the following additional lines:
>>
>>tcp        0      0 192.168.6.14:32822      192.168.6.14:32819      
>>TIME_WAIT
>>tcp        0      0 127.0.0.1:32820         192.168.6.14:2809       
>>TIME_WAIT
>>
>>So it looks like the corba server is binding to 127.0.0.1. I suspect 
>>this is the problem because the 127.0.0.1 address is not available to 
>>the vservers. Is there any way to get a corba server to bind to a 
>>different address?
>>
>>Thanks,
>>
>>Russell
>>    
>>