[omniORB] omniORB <-> other

Duncan Grisby duncan at grisby.org
Fri May 30 15:00:20 BST 2003


On Wednesday 28 May, "Jerome Kerdreux" wrote:

> I need to plug a Ipaq w/ a wifi card to my omniORB system
> 
> As, this is an old Ipaq w/ 32Mo .. I think i gonna
> try another orb that omni on this. What should i try ?

You might be able to run omniORB on that, as long as you can use an up
to date version of gcc. If you definitely need something smaller, I
think ORBit is probably your only option, unless you want to write
your own GIOP code. If you are only doing a little bit of CORBA stuff,
it's not too unreasonable to write the GIOP code.

Unfortunately, ORBit has a history of not being too bothered with spec
compliance...

> omniORB: inputMessage: from giop:tcp:192.44.75.35:47821 96 bytes
> omniORB:
> 4749 4f50 0102 0100 5400 0000 f0f5 ffbf GIOP....T.......
> 0100 0000 0000 0000 1400 0000 ff62 6964 .............bid
> 6972 fe4f abd4 3e01 007c fa00 0000 0000 ir.O..>..|......
> 1300 0000 4f52 4269 745f 6765 745f 7479 ....ORBit_get_ty
> 7065 5f69 6400 4f00 0100 0000 0100 0000 pe_id.O.........
> 0c00 0000 0101 0101 0100 0105 0901 0100 ................
> omniORB:  recieve codeset service context and set TCS to (UTF-8,UTF-16)

This shows ORBit trying to invoke an operation called
"ORBit_get_type_id" on the object.

> omniORB: throw BAD_OPERATION from poa.cc:1749
> (NO,BAD_OPERATION_UnRecognisedOperationName)

omniORB correctly throws BAD_OPERATION, since the operation isn't
defined in your IDL (I assume).

[...]
> omniORB: inputMessage: from giop:tcp:192.44.75.35:47821 96 bytes
> omniORB:
> 4749 4f50 0102 0100 5400 0000 30f6 ffbf GIOP....T...0...
> 0100 0000 0000 0000 1400 0000 ff62 6964 .............bid
> 6972 fe4f abd4 3e01 007c fa00 0000 0000 ir.O..>..|......
> 1300 0000 4f52 4269 745f 6765 745f 7479 ....ORBit_get_ty
> 7065 5f69 6400 4f00 0100 0000 0100 0000 pe_id.O.........
> 0c00 0000 0101 0101 0100 0105 0901 0100 ................
> omniORB:  recieve codeset service context and set TCS to (UTF-8,UTF-16)

ORBit has another go, and incidentally unnecessarily sends the codeset
service context again.

> omniORB: throw BAD_OPERATION from poa.cc:1749
> (NO,BAD_OPERATION_UnRecognisedOperationName)

The operation still doesn't exist.

[...]
> omniORB: throw giopStream::CommFailure from
> giopImpl12.cc:1242(0,NO,COMM_FAILURE_UnMarshalArguments)

ORBit gives up (or crashes) and closes the connection.


You need to find out why ORBit is trying to call a non-existent
operation and if possible, prevent it from doing so.

Cheers,

Duncan.

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



More information about the omniORB-list mailing list