[omniORB] COMM_FAILURE

[Duncan Grisby]

On Wednesday 14 February, Gnanasekaran Thoppae wrote:

[...]
> IOR [1] - *not* working with nameclt but *is* working with enames
> IOR:010000002800000049444c3a6f6d672e6f72672f436f734e616d696e672f4e
> 616d696e67436f6e746578743a312e300001000000000000002400000001010100
> 0d0000003134312e36312e36382e32360000650e040000000100000000000000

This IOR is from an ORB which supports IIOP 1.1. omniORB 3 only
supports 1.0 (1.1 and 1.2 are coming with omniORB 4) so it uses 1.0 to
contact the object. That should work fine, since all ORBs which
support 1.1 are required to support 1.0 too.

The trace you gave shows that omniORB issued a LocateRequest message
on the object, and received an invalid reply. The chances are, the
remote ORB sent a 1.1 reply. You should contact the vendor of the
other ORB, and report the bug. If you want more details of exactly
what went wrong, run omniORB with a command line argument of
-ORBtraceLevel 30. That will print out all the GIOP traffic.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --