[omniORB] Is it possible to suppress the COMM_FAILURE_UnMarshallArguments Exception?

[Duncan Grisby]

On Friday 29 February, cjulwelling at micron.com wrote:

> 	I've been able to reproduce the issue using the provided echo
> (eg3_clt/eg3_impl) examples.  When I run the example code it prints 10
> "Hello" messages and then exits on the client side.  The server side
> then prints out:
> omniORB: Orderly connection shutdown: giop:tcp<ipaddr and port info>
> omniORB: throw giopStream::CommFailure from
> giopImpl12.cc:1367(0,NO,COMM_FAILURE_UnMarshalArguments)

As you say, this is entirely normal. You've chosen to get lots of
tracing messages, and this is one of them. It's a really useful message
to have in cases where you don't expect a connection to be closed. The
code that outputs the message can't possibly know whether you were
expecting the connection to close at that time, so it can't sensibly
suppress the message in those cases.

[...]
> 	My question is, is it possible via a omniORB.cfg setting,
> compile setting, or better practice on my side to eliminate these
> warning messages?  I would really like to suppress the output of these
> messages, but not affect the output of other error messages.

If you're really that bothered by the messages, just comment out the
code that outputs them. But then don't ever send any traces if you
happen to have unexpected connection related problems, because removing
that message will affect the ability to diagnose them.

Cheers,

Duncan.

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