<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jun 7, 2013 at 12:40 AM, sheena kansal <span dir="ltr"><<a href="mailto:sheena.kansal@gmail.com" target="_blank">sheena.kansal@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Thanks for the quick reply.<br><br></div>so another question, we are hitting lot of omni::TRANSIENT_CallTimedOut errors in a recent time.<br>
<br></div>and its happening mostly from these omniORB calls (marked with <----------):<br>
<br><br>-----------------------------------------------------------------------------------------------<br>try<br>{<br> omniORB::setClientCallTimeout(<br> rootContext,15000); <br>
1. o_ObjRef = rootContext->resolve(name); <-------<br>}<br></div>catch(...){}<br>---------------------------------------------------------------------------------------------------<br> omniORB::setClientCallTimeout(<br>
l_readyObjRef,15000);<br>2. if(l_readyObjRef->_non_existent()) <------------<br> {<br> cout<< " sink _non_existent true, object not registered";<br>
}<br>---------------------------------------------------------------------------------------------------<br> iv_Orb = CORBA::ORB_init(argc,argv);<br>3. o_NSObj = iv_Orb->resolve_initial_references(NSTag.c_str()); -<-----------------<br>
<div><div>---------------------------------------------------------------------------------------------------<br><br>Do you think it will be resolved by increasing the clientCallTimeout value from 15 sec to say 60 sec? <br>
or its more appropriate to do a retry? <br></div><div>Or it could be due to some other configuration related setting?<br></div><div>The configuration is there in my previous mail (<a href="http://www.omniorb-support.com/pipermail/omniorb-list/2013-June/031417.html" target="_blank">http://www.omniorb-support.com/pipermail/omniorb-list/2013-June/031417.html</a>)<br>
<br></div><div><br></div><div><br><br><br></div></div></div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On Thu, Jun 6, 2013 at 7:58 PM, Duncan Grisby <span dir="ltr"><<a href="mailto:duncan@grisby.org" target="_blank">duncan@grisby.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Thu, 2013-06-06 at 16:43 +0530, sheena kansal wrote:<br>
<br>
> What will happen if we give timeout using SinkTimeoutMsec() API?<br>
><br>
> for example, we have code like this -<br>
> //const long SinkTimeoutMsec = 15000;<br>
> omniORB::setClientCallTimeout( rootContext,ServerReady::SinkTimeoutMsec);<br>
> o_ObjRef = rootContext->resolve(name);<br>
<br>
</div>If the resolve() call takes more than 15 seconds, the call will result<br>
in a CORBA::TRANSIENT exception. The minor code will be set to the value<br>
omni::TRANSIENT_CallTimedOut.<br>
<div><br>
> what is the value of default timeout?<br>
<br>
</div>There is no default timeout. By default calls never time out, so they<br>
can block forever. When opening a new TCP connection to a server, the<br>
operating system's TCP stack will have a default connection timeout if<br>
the server is not reachable, but that value is usually very long.<br>
<br>
Cheers,<br>
<br>
Duncan.<br>
<span><font color="#888888"><br>
--<br>
Duncan Grisby <<a href="mailto:duncan@grisby.org" target="_blank">duncan@grisby.org</a>><br>
<br>
</font></span></blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br>Regards,<br>Sheena
</font></span></div>
</blockquote></div><br><br clear="all"><br>-- <br>Regards,<br>Sheena
</div></div>