[omniORB] unknown COMM_FAILURE_UnMarshalArguments
Duncan Grisby
duncan at grisby.org
Wed Sep 29 11:51:51 BST 2010
On Wed, 2010-09-29 at 10:13 +0200, Christoph Becker wrote:
> in omniORB 4.1.2 ofter I get UnMarshalArguments exceptions but I cannot see why.
>
> omniORB: inputMessage: from giop:ssl:172.18.50.60:54862 12 bytes
> omniORB:
> 4749 4f50 0102 0105 0000 0000 GIOP........
> omniORB: Orderly connection shutdown: giop:ssl:172.18.50.60:54862
> omniORB: throw giopStream::CommFailure from
> giopImpl12.cc:1370(0,NO,COMM_FAILURE_UnMarshalArguments)
> omniORB: Server connection refcount = 1
> omniORB: Server connection refcount = 0
> omniORB: Server close connection from giop:ssl:172.18.50.60:54862
>
> For me it looks like a normal CloseConnection request (05 in byte 8)
> in little endian (01 in byte 7).
That is a normal CloseConnection message, and omniORB has handled it
normally. The exception isn't propagated out to application code -- it
is handled inside omniORB. Notice that the exception is the internal
giopStream::CommFailure class, not a CORBA exception.
Cheers,
Duncan.
--
-- Duncan Grisby --
-- duncan at grisby.org --
-- http://www.grisby.org --
More information about the omniORB-list
mailing list