[omniORB] AW: How to guard against endless loops in the server?

[Pfeiffer Daniel]

On Jan 26, in "retries with omniorb 4?" Adrian Rosoga <arosoga@yahoo.com>
cited an older reply from Duncan which might also be an answer to this
question.  However a transiently lost connection would only account for 1
retry?

Daniel
this morning I wrote:
> We want to guard against endless loops in the server with a server side
> timeout.  I would expect this to work by interrupting the server method
> and
> sending an exception to the client (which is operating with a longer
> timeout).
> 
> Instead my trace output suggests that the server is indeed being
> interrupted(?), but is being reentered straight away.  I haven't figured
> out
> how often it is being reentered -- about 3 to 5 times.  Looks like this
> might
> be bounded by serverCallTimeOutPeriod * scanGranularity.
> 
> The documentation of serverCallTimeOutPeriod in version 4, sounds like the
> semantics have completely changed since version 3.0.5.  Anyway: What is
> the
> correct way to guard against runaway server methods in both 3.0.5 and 4.0?