[omniORB] serious endPoint problem on AIX platform

Mark Zimmerman markzimm at frii.com
Fri May 21 11:05:35 BST 2004


On Fri, May 21, 2004 at 10:02:28AM +0200, Tomasz Bech wrote:
> Hi all,
> Platform: AIX 4.3 and 5.2. omniORB 4.0.2
> 
> Last time we encounter serious problem when we use endPoint:
> -ORBendPoint giop:tcp:129.184.99.18:40005
> 
> and servers shows:
> ....
>    endPoint = giop:tcp:129.184.99.18:40005
> .....
> 
> Error: Unable to create an endpoint of this description: giop:tcp:129.1
> 84.99.18:40005
> omniORB: throw INITIALIZE from objectAdapter.cc:244 
> (NO,INITIALIZE_TransportErro
> r)
> omniORB: throw INITIALIZE from corbaBoa.cc:211 (NO,INITIALIZE_FailedBOAInit)
> 
> I'm sure that port is not busy! Further more when I use endPoint like:
> -ORBendPoint giop:tcp::40005
> it WORKS!       
> (but we need to specify exact ip, because of several ethernet interfaces).
> 
> The same works ok on Linux.
> 
> 
> What strange is that omniNames started with similar endPoint works! All 
> is compiled using the same libraries.
> 
> Where is the problem?
> (Maybe it is fixed in 4.0.3 - if so, which part of the code?)

Do this:

grep SIOCGIFCONF src/lib/omniORB/orbcore/tcp/tcpTransportImpl.cc

If you do not get this as your result:

#  define OMNI_SIOCGIFCONF OSIOCGIFCONF
#  define OMNI_SIOCGIFCONF SIOCGIFCONF
    if ( ioctl(sock, OMNI_SIOCGIFCONF, &ifc) < 0 ) {
  if (ioctl (s, SIOCGIFCONF, (int)&ifc) < 0) {


Then that is your problem.

-- Mark



More information about the omniORB-list mailing list