[omniORB] CommFailure from giopStream.cc:874(0, NO, COMM_FAILURE_UnMarshalArguments)

Duncan Grisby duncan at grisby.org
Tue Apr 29 21:51:36 BST 2008

On Tuesday 29 April, "Gundogi, Sashidher" wrote:

> The Object implementation client is connecting to the naming server and
> it is creating IORs for my objects and then it is also loosing the
> connection with orb naming with below error.
> omniORB: Error in network receive (start of message):
> giop:tcp:[::ffff:(my ip)]:4677
> omniORB: throw giopStream::CommFailure from
> giopStream.cc:874(0,NO,COMM_FAILURE_UnMarshalArguments)
> omniORB: Orderly connection shutdown: giop:tcp:[::ffff:(my ip)]:4678
> omniORB: throw giopStream::CommFailure from
> giopImpl12.cc:1370(0,NO,COMM_FAILURE_UnMarshalArguments)

That is not an error. It is just the server noticing a client going
away. The exception is handled internally inside omniORB, and is not
propagated to application code.

What are the symptoms of the actual problem you are seeing?


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

More information about the omniORB-list mailing list