|
From: Leif M. <le...@ta...> - 2006-04-10 02:20:48
|
Anat,
The ability to disable restarts does interest other users, this is
why I added the
wrapper.disable_restarts property:
http://wrapper.tanukisoftware.org/doc/english/prop-disable-restarts.html
The problem is that in your case, you would like a combination. You
would
like to allow one restart, if it was requested from the JVM, but no others.
Let me think about it. I may need a property to deal with all
non-WrapperManager.restart() restarts.
Cheers,
Leif
Anat Halpern wrote:
> Leif and David - thanks for the quick replies.
>
> Leif Mortenson wrote:
>> 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.
> I understand this. In my case, however, I don't want to allow any
> crashes of the application. In any case, I'd like to know of these
> crashes, so I could fix the bugs causing them. This is especially
> importance in a service version, where people are likely to forget
> that the application is even running, and so wouldn't notice frequent
> crashes, as long as the application restarts.
>
> I have no problem using the workaround of setting a large value for
> max invocations, if you don't think this could interest other people.
>
> Cheers,
> Anat
|