[omniORB] TCP timeout delay when host is unreachable

[renny.koshy at rubixinfotech.com]

Thomas,

You can setup PER CALL timeouts in omniORB that is diff from this... we do 
this so that the INITIAL RESOLUTION of the object takes X ms, and we make 
function calls that last several seconds at times.

Renny Koshy
President & CEO

--------------------------------------------
RUBIX Information Technologies, Inc.
www.rubixinfotech.com




thomas.hautesserres at kodak.com
Sent by: omniorb-list-bounces at omniorb-support.com
09/28/2004 08:23 AM

 
        To:     jay.welch at transcore.com
        cc:     omniorb-list at omniorb-support.com
        Subject:        RE: [omniORB] TCP timeout delay when host is unreachable



Thanks for your reply, but this doesn't apply to our problem: we don't 
want
to have a time out in general calls (as some can be quite long), only for
connection attempts.

This tcp connect time out is a general problem on Solaris (not only for
omniORB) that can be resolved by modifying the code managing the socket,
but in omniORB case, I've hoped for an easier solution...

Thomas


> Jay Welch wrote:
> Try looking at section 8.3.1 in the omniORB.pdf. This is explains how to
set the ClientCallTimeout value a few
> different ways. I have with other ORBs but not omniORB used specific
policies to set this same value. The interface omniORB provides is much
> simpler. Hope this helps.

-----Original Message-----
From: thomas.hautesserres at kodak.com
[mailto:thomas.hautesserres at kodak.com]
Sent: Tuesday, September 28, 2004 7:34 AM
To: omniorb-list at omniorb-support.com
Subject: [omniORB] TCP timeout delay when host is unreachable


Hi,

We are using omniORB 4.0.2 on both Solaris and Windows.

We have a problem occuring only for Solaris processes : when an object
reference points to an unreachable host (usually our Naming Service host,
acessed through a corbaname URL), it takes up to 3 minutes for the CORBA
call to return.

As having unreachable remote sites is part of the "normal" situation for
our application (or at least should be supported without large performance
impact), this is somehow not acceptable.

Before sending this mail, I have search the omniORB mailing list archive
and found an email for 1998 about the exact same problem. Here:
http://www.omniorb-support.com/pipermail/omniorb-list/1998-October/011748.html


I was wondering:
- First, is there any new configuration item to workaround this problem on
Solaris, either in omniORB or maybe in Solaris system settings?
- If not, if the patch described in the old email still applicable?

Thanks a lot,

Thomas


_______________________________________________
omniORB-list mailing list
omniORB-list at omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list



_______________________________________________
omniORB-list mailing list
omniORB-list at omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20040928/a69e5a04/attachment-0001.htm