[omniORB] Cannot connect to omniNames with MICO client

[p.klotz@icoserve.com]

I tried to contact the omniORB Naming Service via a MICO client but the
only thing I get is a CORBA::ORB::InvalidName exception in the client's
resolve_initial_references() call.
Everything works fine when using an omniORB client.

The omniNames command line is
./omniNames -ORBendPoint giop:tcp:perseus:8888 -ORBmaxGIOPVersion 1.0
-ORBtraceLevel 40

I don't know if MICO speaks GIOP higher than 1.0 but even different values
do not make any difference.

Below is the debug output of omniNames when
    a) using a MICO client
    b) using an omniORB client

a) Connecting to omniNames via a client using MICO:

     omniORB: Accepted connection from giop:tcp:10.16.34.103:33248 because
of this rule: "* unix,ssl,tcp"
     omniORB: inputMessage: from giop:tcp:10.16.34.103:33248 103 bytes
     4749 4f50 0100 0100 5b00 0000 0000 0000 GIOP....[.......
     0100 0000 0100 0000 0000 0000 0600 0000 ................
     5f62 696e 6400 0000 0000 0000 2800 0000 _bind.......(...
     4944 4c3a 6f6d 672e 6f72 672f 436f 734e IDL:omg.org/CosN
     616d 696e 672f 4e61 6d69 6e67 436f 6e74 aming/NamingCont
     6578 743a 312e 3000 0b00 0000 4e61 6d65 ext:1.0.....Name
     5365 7276 6963 65                       Service
     omniORB: throw OBJECT_NOT_EXIST from GIOP_S.cc:318
(NO,OBJECT_NOT_EXIST_NoMatch)
     omniORB: sendChunk: to giop:tcp:10.16.34.103:33248 76 bytes
     4749 4f50 0100 0101 4000 0000 0000 0000 GIOP....@.......
     0100 0000 0200 0000 2700 0000 4944 4c3a ........'...IDL:
     6f6d 672e 6f72 672f 434f 5242 412f 4f42 omg.org/CORBA/OB
     4a45 4354 5f4e 4f54 5f45 5849 5354 3a31 JECT_NOT_EXIST:1
     2e30 0000 0100 4d4f 0100 0000           .0....MO....
     omniORB: throw giopStream::CommFailure from
giopStream.cc:812(0,NO,COMM_FAILURE_UnMarshalArguments)
     omniORB: Server connection refcount = 1
     omniORB: Server connection refcount = 0


b) Connecting to omniNames via a client using omniORB:

     omniORB: Accepted connection from giop:tcp:10.16.34.103:33256 because
of this rule: "* unix,ssl,tcp"
     omniORB: inputMessage: from giop:tcp:10.16.34.103:33256 100 bytes
     4749 4f50 0100 0100 5800 0000 0000 0000 GIOP....X.......
     0200 0000 0100 0000 0b00 0000 4e61 6d65 ............Name
     5365 7276 6963 6500 0600 0000 5f69 735f Service....._is_
     6100 0000 0000 0000 2800 0000 4944 4c3a a.......(...IDL:
     6f6d 672e 6f72 672f 436f 734e 616d 696e omg.org/CosNamin
     672f 4e61 6d69 6e67 436f 6e74 6578 743a g/NamingContext:
     312e 3000                               1.0.
     omniORB: sendChunk: to giop:tcp:10.16.34.103:33256 25 bytes
     4749 4f50 0100 0101 0d00 0000 0000 0000 GIOP............
     0200 0000 0000 0000 01                  .........
     omniORB: inputMessage: from giop:tcp:10.16.34.103:33256 157 bytes
     4749 4f50 0100 0100 9100 0000 0000 0000 GIOP............
     0400 0000 0100 0000 0b00 0000 4e61 6d65 ............Name
     5365 7276 6963 6500 0800 0000 7265 736f Service.....reso
     6c76 6500 0000 0000 0400 0000 0a00 0000 lve.............
     5465 7374 4472 6976 6500 734e 0100 0000 TestDrive.sN....
     002f 4e61 0600 0000 486f 7374 7300 743a ./Na....Hosts.t:
     0100 0000 0000 0000 0a00 0000 6963 6f66 ............icof
     6c75 6666 7900 0000 0100 0000 0000 0000 luffy...........
     1100 0000 5465 7374 4472 6976 6553 7065 ....TestDriveSpe
     6369 616c 0000 0000 0100 0000 00        cial.........
     omniORB: sendChunk: to giop:tcp:10.16.34.103:33256 172 bytes

Has somebody an idea why the first connection attempt fails?

Best regards, Peter.