[omniORB] COMM_FAILURE_MarshalArguments
Duncan Grisby
duncan at grisby.org
Wed Oct 27 15:40:16 BST 2010
On Wed, 2010-09-29 at 13:26 +0200, Christoph Becker wrote:
> Now I caught an exception that I cannot analyse, why it is thrown.
>
> omniORB: Switch rope to use address giop:tcp:172.18.50.36:2809
> omniORB: Error in network send: giop:tcp:255.255.255.255:65535
> omniORB: throw giopStream::CommFailure from
> giopStream.cc:1182(0,NO,COMM_FAILURE_MarshalArguments)
> omniORB: Client connection refcount = 0
> omniORB: Client close connection to giop:tcp:255.255.255.255:65535
> omniORB: throw COMM_FAILURE from omniObjRef.cc:784
> (NO,COMM_FAILURE_MarshalArguments)
That's a TCP connection closure by the server being noticed by the
client and turned into a COMM_FAILURE exception. The bogus IP address
and port information is due to a logging bug in omniORB that was fixed
in 4.1.3 or so.
Cheers,
Duncan.
--
-- Duncan Grisby --
-- duncan at grisby.org --
-- http://www.grisby.org --
More information about the omniORB-list
mailing list