[omniORB] timeouts and config file question

[Vincent Joseph]

Hi,

Yesterday we switched over from MICO to omniORB2.8.0 (yep
it took just one day) 
Biggest issues were:
1) the case sensitivity of the idl files
2) modifying header files to use base class name of
_sk_BASECLASS (omni), instead of BASECLASS_skel_ (mico).
3) a few lines of code changes (~2 per client/impl file)
[changes were #ifdef if we need to go back]

Everything is up and running with just one quirk.

Some of our remote calls take an awful long time to
complete. It appears that the services are
getting CORBA_COMM failures (timeout?) as a result of 
these long running calls. Reading through the 
documentation, I noticed the following two options.
-ORBclientCallTimeOutPeriod <0-max integer> 
-ORBserverCallTimeOutPeriod <0-max integer> 
Will the above help solve the timeout issue?

And can I place the options in the omni config file,
instead of supplying them on the command line ?

Thanks,

Vincent
-- 
Water vapor gets together in a cloud. When it 
is big enough to be called a drop, it does.