Discussion:
[omniORB] unknown COMM_FAILURE_UnMarshalArguments
Christoph Becker
2010-09-29 14:13:39 UTC
Permalink
Hi,

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).

Any help welcome.

Cheers, Christoph
Duncan Grisby
2010-09-29 15:51:55 UTC
Permalink
Post by Christoph Becker
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
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 --
-- ***@grisby.org --
-- http://www.grisby.org --
Loading...