Re: [Wrapper-user] restart tuning

[Anat H. <an...@en...>]

Thanks for your help, Leif.

The first option is problematic, as the crash is not time-dependent.
As for the option of using disable.restarts, I have to be able to call 
WrapperManager.restart explicitly, at least once, (this is my workaround 
for the GUI problem we discussed before - I restart the application 
after I'm done with the GUI).
So to make this clear, the problem is: explicit restarts are required, 
but I'd still like to limit number of restarts on account of failure in 
the run.

According to the description of  max_failed_invocations: " Maximum 
number of times that the Wrapper will attempt to restart the JVM if each 
attempted invocation exits abnormally or...". In my case, the JVM exists 
abnormally each time, but still the time factor is considered. Is it 
possible to disregard the time and consider only the success/failure of 
the run? If not, I think the documentation should be changed a bit.

Thanks a lot,
Anat

Leif Mortenson wrote:
> Anat,
>    If you use the wrapper.max_failed_invocations=1 property, you
> will also need to set the wrapper.successful_invocation_time property to
> a large value as you said.
> http://wrapper.tanukisoftware.org/doc/english/prop-max-failed-invocations.html 
>
> http://wrapper.tanukisoftware.org/doc/english/prop-successful-invocation-time.html 
>
>
>    Good news is that as of 3.2.0, there is a better way:
> http://wrapper.tanukisoftware.org/doc/english/prop-disable-restarts.html
>
>    The only difference from your request is that all restarts are 
> treated the
> same way.  This is true with the above properties as well.
>
> Cheers,
> Leif
>
> Anat Halpern wrote:
>> Hi all,
>> I'd like to disable all restarts except for explicit calls to 
>> WrapperManager - is this possible?
>>
>> I've also tried to use the wrapper.max_failed_invocations, and it did 
>> not work as I expected it to - the application kept  running for a 
>> while before crashing, so it was considered a successful invocation. 
>> Is there any way of making the wrapper ignore the 
>> successful_invocation_time property (except setting it to a really 
>> large number)?
>>
>> The problem I'm trying to deal with is that the application runs, and 
>> then, depending on the input, crashes. The wrapper handled this 
>> situation by restarting the application over and over, despite the 
>> wrapper.max_failed_invocations=2.
>> Any suggestions?
>>
>> Many thanks,
>> Anat
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting 
> language
> that extends applications into web and mobile media. Attend the live 
> webcast
> and join the prime developer group breaking into this new coding 
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
> +++++++++++++++++++++++++++++++++++++++++++
> This Mail Was Scanned By Mail-seCure System
> at the Tel-Aviv University CC.