[omniORB] implementing CORBA timeouts

[Andrew Knapp]

Thanks for the quick response.

I tried the following settings both in my omniORB.cfg file as well as
passing them as command line parameters when calling the ORB.init(), but
the timeouts do not seem to be taking effect.

My script lists all of the contexts/factories registered in the naming
service.   The script gets a list of IORs from the NameService then I
try to narrow those IORs to a CORBA.Object.   If the narrow fails, I
mark the factory as 'down' and a successful narrow will mark it as up.

The problem I'm having is with this narrow call.   Despite the timeouts
I've set in my omniORB.cfg, the narrow still takes much longer than the
sepecificed timeout when trying to narrow a factory that isn't 'on the
wire'.

Here's my omniORB.cfg:

InitRef=NameService=corbaname::NameServer:5000
scanGranularity = 5
clientCallTimeOutPeriod = 2000
serverCallTimeOutPeriod = 2000

What am I missing?

-ADK



-----Original Message-----
From: Duncan Grisby [mailto:duncan at grisby.org] 
Sent: Thursday, July 15, 2004 5:17 AM
To: Andrew Knapp
Cc: omniorb-list at omniorb-support.com
Subject: Re: [omniORB] implementing CORBA timeouts 

On Wednesday 14 July, "Andrew Knapp" wrote:

> I need to implement CORBA timeouts in one of my programs. I saw in the
> manual where it mentioned some options such as
> -ORBclientCallTimeOutPeriod and -ORBserverCallTimeOutPeriod-however, I
> did not see any examples on how to use them.
> 
> 1.	Are there any options that you can place into omniORB.cfg to set
> timeouts on CORBA calls?

Yes, just put entries of clientCallTimeOutPeriod, etc. in
omniORB.cfg.  Look at sample.cfg and section 8.3 of the omniORB
manual:

  http://omniorb.sourceforge.net/omni40/omniORB/omniORB008.html#toc38

> 2.	How do you pass command line options to the orb when running
> your actual python script?

Pass them to ORB_init.

Cheers,

Duncan.

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