Re: CosNaming bind problem

[Frank Rehberger <Frank Rehberger web de>]

Jean PYLOUSTER wrote:
 > Hello,
 >
 >      I work with orbit 0.5.8-4.
 >      I wrote a program with a server, a client and a Naming Service.
 >      When all run on one machine, it's ok. But, when I run Naming
 >      Service on one machine and the server on another one, server
 >      found the Naming Server with the IOR but I got a error message
 >      "<IDL:CORBA/COMM_FAILURE:1.0>" when the server bind into the
 >      naming server.
 >
 >      I active the option -ORBIIOPIPv4 = 1 and -ORBIIOPIPUSock = 0 with
 >      the server and the client and I use NFS to read the IOR of the
 >      Naming Service (Classic ...)

decoding with 'ior-decode-2' the IOR you sent me, it looks like this:

Object ID: IDL:omg.org/CosNaming/NamingContext:1.0
IOP_TAG_ORBIT_SPECIFIC: usock /tmp/orbit-bioinfo/orb-7304838211985670747
IPv6 port 0
      object_key (24) '0000000024a38e0b4afd9427010000004f6cd3b42abd73db'

IOP_TAG_INTERNET_IOP: GIOP 1.0 193.54.201.97:32835
      object_key (24) '0000000024a38e0b4afd9427010000004f6cd3b42abd73db'

It contains a unix socket profile only valid on you local machine. One
commandline parameter is wrong (see
http://orbit-resource.sourceforge.net/faq.html#orbit), try:
   -ORBIIOPIPv4=1 -ORBIIOPUSock=0

Hope this helps.