[omniORB] Valuetype factory issue omniiORBpy

Duncan Grisby duncan at grisby.org
Fri Jul 22 13:35:59 BST 2005


On Thursday 21 July, Jonathan Walsh wrote:

[...]
> omniORB: sendChunk: to giop:tcp:166.17.242.101:34817 244 bytes
> omniORB:
> 4749 4f50 0102 0100 e800 0000 0800 0000 GIOP............
> 0300 0000 0000 0000 2300 0000 1401 0f00 ........#.......
> 4e53 545f 01e0 426e dc03 0001 0000 0001 NST_..Bn........
> 0000 0001 0000 0001 0000 0002 0000 0020 ...............
> 1200 0000 636f 6e6e 6563 745f 636f 6d70 ....connect_comp
> 5f64 6174 6100 3d20 0000 0000 0100 0000 _data.= ........

This shows omniORB calling an operation called connect_comp_data...

> omniORB: inputMessage: from giop:tcp:166.17.242.101:34817 72 bytes
> omniORB:
> 4749 4f50 0102 0101 3c00 0000 0800 0000 GIOP....<.......
> 0100 0000 0000 0000 2c00 0000 4944 4c3a ........,...IDL:
> 6f6d 672e 6f72 672f 436f 6d70 6f6e 656e omg.org/Componen
> 7473 2f41 6c72 6561 6479 436f 6e6e 6563 ts/AlreadyConnec
> 7465 643a 312e 3000                     ted:1.0.

The operation raises a user exception of Components::AlreadyConnected...

> omniORB: throw UNKNOWN from pyCallDescriptor.cc:233
> (NO,UNKNOWN_UserException)

But omniORB thinks the exception was not declared in the IDL, so it
throws a CORBA::Unknown exception.

You should check that the idl on client and server match each other.

This is a different problem to the one you originally mentioned, where
you were getting an exception about having no value factory.

Cheers,

Duncan.

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



More information about the omniORB-list mailing list