[omniORB] Catching Invocations That Timeout

[Duncan Grisby]

On Monday 11 March, Wilson Jimmy - jiwils wrote:

> I have a python application using omniORBpy 1.4 that has some object
> references that do not respond to _non_existent with the timeout period of
> two seconds.
> 
> I am specifying that timeout in my call to ORB_init(...) like so:
> 
> argv = ['', '-ORBclientCallTimeOutPeriod', '2']
> self.ORB = CORBA.ORB_init(argv, CORBA.ORB_ID)
> 
> Is there a way for me to know that a timeout occurred versus when the call
> to _non_existent just returns a COMM_FAILURE or something similar?

Not with omniORBpy 1.x. With omniORBpy 2.x (based on omniORB 4.0.x)
exceptions have meaningful minor codes. You can use the minor codes to
find out the reason for a particular exception.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --