[omniORB] CORBA::TRANSIENT default exception handler clarification

[Manusha Wijekoon]

hi,
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? 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.

Does that mean, in version 4.0, the flexibility of controlling the maximum
re-tries is removed?

thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20081117/b1249f46/attachment.htm

[Duncan Grisby]

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.