hi,<br>im using omniORB 4.0. according to the users guide (<a href="http://omniorb.sourceforge.net/omni40/omniORB.pdf">http://omniorb.sourceforge.net/omni40/omniORB.pdf</a>) section 4.7.2, this is how CORBA::TRANSIENT exception is handled.<br>
<br>"......... the object's original location. If the retry results in another LOCATION_FORWARD,<br>to the same or a different location, and that forwarded location fails immediately,<br>the TRANSIENT exception will occur again, and the pattern will repeat. With repeated<br>
exceptions, the handler starts adding delays before retries, with exponential<br>back-off ............. "<br><br><br>according to this, the retry "never" gives up? im asking this question because i found a different discription in here (<a href="http://www.cl.cam.ac.uk/research/dtg/attarchive/omniORB/doc/3.0/omniORB/omniORB006.html">http://www.cl.cam.ac.uk/research/dtg/attarchive/omniORB/doc/3.0/omniORB/omniORB006.html</a>).<br>
According to this document, "............ When a <tt>CORBA::TRANSIENT</tt> exception is raised by the ORB runtime,
the default behaviour of the proxy objects is to retry indefinitely
until the operation succeeds. Successive retries will be delayed
progressively by multiples of
<tt>omniORB::defaultTransientRetryDelayIncrement</tt>. The delay
will be limited to the maximum specified by
<font size="2"><tt>omniORB::defaultTransientRetryDelayMaximum</tt></font>. The unit of both
values are in seconds. ........... ". <br>I think this documentation is about omniORB 3.0.<br><br>Does that mean, in version 4.0, the flexibility of controlling the maximum re-tries is removed?<br><br>thanks.<br><br>