[omniORB] protocol of communication between javaorb and omniORB

[Duncan Grisby]

On Tuesday 16 November, "Diez B. Roggisch" wrote:

[...]
> omniORB: inputMessage: from giop:tcp:192.168.1.3:35588 66 bytes
> omniORB:
> 4749 4f50 0102 0000 0000 0036 0000 0005 GIOP.......6....
> 0300 0000 0000 0000 0000 000e fed7 0b9a ................
> 4100 003e f100 0000 0001 0000 0000 0004 A..>............
> 6765 7400 0000 0000 0000 0005 7465 7374 get.........test
> 0000                                    ..
> omniORB: Garbage left at the end of input message from 
> giop:tcp:192.168.1.3:35588
> omniORB: From endpoint: giop:tcp:192.168.1.3:35588. Detected GIOP 1.2 protocol 
> error in input 
> message. ../../../../../src/lib/omniORB/orbcore/giopImpl12.cc:789. Connection 
> is closed.

omniORB thinks there is more data in that message than there should
be. One possibility is that omniORB and the Java ORB have seen different
versions of the IDL. Other than that, either the Java ORB is really
sending too much, or omniORB is wrong in thinking there's too much. To
find out, what is the IDL definition of the get operation you're
calling?

Cheers,

Duncan.

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