[omniORB] ConnectionFailure exception in IDL causes problems...

[Duncan Grisby]

On Thursday 25 September, scott.rediger at teradyne.com wrote:

> Herein lies the problem: when my servant throws the IDL ConnectionFailure
> exception, fully-scoped (A::B::ConnectionFailure), the client's catch block
> for A::B::ConnectionFailure is not "catching" but rather the catch-all case
> CORBA::Exception is "catching".
> 
> If I change the IDL exception "ConnectionFailure" to "ConnectionProblem"
> and the servant and client code change to catch this exception, it works
> every time!

Bizarre!

> It appears as if there is a namespace issue with ConnectionFailure within
> omniORB-4.0.1 or within the OS. However, I have done a grep for
> ConnectionFailure inside all header and cc files under omniORB-4.0.1 and
> found nothing, so I am perplexed.

You are right that omniORB doesn't have an exception called
ConnectionFailure. Even if it did, I don't see how it would cause the
problem you were seeing.

Can you get a trace with traceLevel 40 to see what exception is being
sent?

Cheers,

Duncan.

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