[omniORB] CORBA::TRANSIENT default exception handler
clarification
Duncan Grisby
duncan at grisby.org
Fri Dec 12 12:33:57 GMT 2008
On Monday 17 November, "Manusha Wijekoon" wrote:
> im using omniORB 4.0. according to the users guide (http://
> omniorb.sourceforge.net/omni40/omniORB.pdf) section 4.7.2, this is how
> CORBA::TRANSIENT exception is handled.
>
> "......... the object's original location. If the retry results in another
> LOCATION_FORWARD,
> to the same or a different location, and that forwarded location fails
> immediately,
> the TRANSIENT exception will occur again, and the pattern will repeat. With
> repeated
> exceptions, the handler starts adding delays before retries, with exponential
> back-off ............. "
>
> according to this, the retry "never" gives up?
Yes, it never gives up.
If you want it to give up, just register your own handler that limits
the number of retries.
> im asking this question because
> i found a different discription in here (http://www.cl.cam.ac.uk/research/dtg/
> attarchive/omniORB/doc/3.0/omniORB/omniORB006.html).
> According to this document, "............ When a CORBA::TRANSIENT 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
> omniORB::defaultTransientRetryDelayIncrement. The delay will be limited to the
> maximum specified by omniORB::defaultTransientRetryDelayMaximum. The unit of
> both values are in seconds. ........... ".
> I think this documentation is about omniORB 3.0.
That setting didn't limit the number of times it retried. It just meant
you could specify the maximum amount of delay between retries.
Cheers,
Duncan.
--
-- Duncan Grisby --
-- duncan at grisby.org --
-- http://www.grisby.org --
More information about the omniORB-list
mailing list