Re: [Wrapper-user] restart tuning

[Leif M. <le...@ta...>]

Anat Halpern wrote:
> Yeah, I can set a very long time, no problem, and also using 0 as 
> indefinite time should work, but this looks more like a workaround 
> (which will work fine for now).
> I would have expected the wrapper to count the number of abnormal 
> terminations, regardless of the run time before this crash. BTW, this 
> is what I understood from the docs. If for example, an application 
> analyzes an input file and crashes on a specific input, (let's say 
> near the end of the file), then it will crash continuously.
That is why there is the max invocations.   It defaults to a value 
larger than 1 to support
port binding problems on solaris systems where a port could fail to bind 
the first few
invocations and then succeed after the 4th restart.  If tomcat crashes, 
its ports may
remain bound for 2 minutes and prevent future restarts.

In most cases, setting a hard number of restarts of 5 would be bad for 
an application
that crashes once in a while.  It would restart 5 times over say a month 
and then
suddenly fail to come up a 6th time.  This is why the successful 
invocation time
exists to allow this counter the be reset.

Cheers,
Leif