[omniORB] Unable to connect omniORB apps to ORBexpress NameService.

[Duncan Grisby]

On Thursday 4 November, dahaverk at rockwellcollins.com wrote:

> When I try to connect to the omniNames service.   This is what I see.
> Note: What is causing the "COMM_FAILURE" in the omniORB GIOP Marshalling?
> Does this mean I have a miss match of UTF-8 vs UTF-16 or something else?
> I'm assuming it's getting the GIOP version matched...

The COMM_FAILURE isn't a problem. It's just omniORB noticing that the
client has closed the connection. It isn't an error.

The problem is this...

> 4749 4f50 0100 0003 0000 002c 0000 0001 GIOP.......,....
> 0000 0024 b541 24b6 4578 7072 6573 734e ...$.A$.ExpressN
> 616d 6573 b5b5 526f 6f74 504f 41b5 4e61 ames..RootPOA.Na
> 6d69 6e67 526f 6f74                     mingRoot
> omniORB: Handling a GIOP LOCATE_REQUEST.

As the log says, this is a LOCATE_REQUEST message, for the object with
key "ExpressNames..RootPOA.NamingRoot" (where the . characters are
byte value 0xb5, not literal . characters). That is not the object key
for omniNames' root naming context, so...

> omniORB: sendChunk: to giop:tcp:192.168.139.16:1032 20 bytes
> omniORB:
> 4749 4f50 0100 0104 0800 0000 0100 0000 GIOP............
> 0000 0000                               ....

omniORB replies with a status of UNKNOWN_OBJECT.

> omniORB: throw giopStream::CommFailure from
> giopStream.cc:828(0,NO,COMM_FAILURE_UnMarshalArguments)

This just shows that the client has closed the connection.

I don't know how you configure ORBexpress, but you need to tell it to
look for the standard key "NameService", not the key it's using.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --