<br><font size=2 face="sans-serif">Thomas,</font>
<br>
<br><font size=2 face="sans-serif">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.</font>
<br>
<br><font size=2 face="sans-serif">Renny Koshy<br>
President & CEO<br>
<br>
--------------------------------------------<br>
RUBIX Information Technologies, Inc.<br>
www.rubixinfotech.com</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>thomas.hautesserres@kodak.com</b></font>
<br><font size=1 face="sans-serif">Sent by: omniorb-list-bounces@omniorb-support.com</font>
<p><font size=1 face="sans-serif">09/28/2004 08:23 AM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To: jay.welch@transcore.com</font>
<br><font size=1 face="sans-serif"> cc: omniorb-list@omniorb-support.com</font>
<br><font size=1 face="sans-serif"> Subject: RE: [omniORB] TCP timeout delay when host is unreachable</font></table>
<br>
<br>
<br><font size=2 face="Courier New"><br>
Thanks for your reply, but this doesn't apply to our problem: we don't want<br>
to have a time out in general calls (as some can be quite long), only for<br>
connection attempts.<br>
<br>
This tcp connect time out is a general problem on Solaris (not only for<br>
omniORB) that can be resolved by modifying the code managing the socket,<br>
but in omniORB case, I've hoped for an easier solution...<br>
<br>
Thomas<br>
<br>
<br>
> Jay Welch wrote:<br>
> Try looking at section 8.3.1 in the omniORB.pdf. This is explains how to<br>
set the ClientCallTimeout value a few<br>
> different ways. I have with other ORBs but not omniORB used specific<br>
policies to set this same value. The interface omniORB provides is much<br>
> simpler. Hope this helps.<br>
<br>
-----Original Message-----<br>
From: thomas.hautesserres@kodak.com<br>
[mailto:thomas.hautesserres@kodak.com]<br>
Sent: Tuesday, September 28, 2004 7:34 AM<br>
To: omniorb-list@omniorb-support.com<br>
Subject: [omniORB] TCP timeout delay when host is unreachable<br>
<br>
<br>
Hi,<br>
<br>
We are using omniORB 4.0.2 on both Solaris and Windows.<br>
<br>
We have a problem occuring only for Solaris processes : when an object<br>
reference points to an unreachable host (usually our Naming Service host,<br>
acessed through a corbaname URL), it takes up to 3 minutes for the CORBA<br>
call to return.<br>
<br>
As having unreachable remote sites is part of the "normal" situation for<br>
our application (or at least should be supported without large performance<br>
impact), this is somehow not acceptable.<br>
<br>
Before sending this mail, I have search the omniORB mailing list archive<br>
and found an email for 1998 about the exact same problem. Here:<br>
http://www.omniorb-support.com/pipermail/omniorb-list/1998-October/011748.html<br>
<br>
<br>
I was wondering:<br>
- First, is there any new configuration item to workaround this problem on<br>
Solaris, either in omniORB or maybe in Solaris system settings?<br>
- If not, if the patch described in the old email still applicable?<br>
<br>
Thanks a lot,<br>
<br>
Thomas<br>
<br>
<br>
_______________________________________________<br>
omniORB-list mailing list<br>
omniORB-list@omniorb-support.com<br>
http://www.omniorb-support.com/mailman/listinfo/omniorb-list<br>
<br>
<br>
<br>
_______________________________________________<br>
omniORB-list mailing list<br>
omniORB-list@omniorb-support.com<br>
http://www.omniorb-support.com/mailman/listinfo/omniorb-list<br>
</font>
<br>
<br>