Discussion:
[omniORB] General exception catched: CORBA.COMM_FAILURE(omniORB.COMM_FAILURE_UnMarshalResults, CORBA.COMPLETED_YES)
Holger Angele
2013-03-15 09:23:13 UTC
Permalink
An HTML attachment was scrubbed...
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20130315/9922e63f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: raise_test.zip
Type: application/zip
Size: 33222 bytes
Desc: not available
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20130315/9922e63f/attachment-0001.zip>
Duncan Grisby
2013-05-23 14:46:12 UTC
Permalink
omniORB: From endpoint: giop:tcp:172.20.136.43:6022. Detected GIOP 1.2
protocol error in input message. giopImpl12.cc:885. Connection is
closed.
CORBA.COMM_FAILURE(omniORB.COMM_FAILURE_UnMarshalResults,
CORBA.COMPLETED_YES)
For reproducing this error I made a little application which you found
in the appending zip-file.
Hi Holger,

Sorry for taking so long to look at this, and thanks for sending an
easy-to-reproduce test case.

There is a bug in the calculation of message offsets that affects the
marshalling of valuetypes when the message size is pre-calculated, and
the message is big enough to span multiple output buffers. I've fixed it
in svn, and it will be in the omniORB 4.1.7 release, in the near future.

Cheers,

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