Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Wed, 3 Jun 2015 21:50:38 +0000 (UTC)
From: "Brett Delle Grazie (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12835219.1433367998000.4757.1433368238032@Atlassian.JIRA>
In-Reply-To: <JIRA.12835219.1433367998000@Atlassian.JIRA>
References: <JIRA.12835219.1433367998000@Atlassian.JIRA>
 <JIRA.12835219.1433367998922@arcas>
Subject: [jira] [Updated] (DAEMON-334) Specify a maximum limit for automatic
 restarts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DAEMON-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Delle Grazie updated DAEMON-334:
--------------------------------------
    Description: 
Our particular use-case requires that JSVC not automatically restart the daemon if the child process throws a fatal error (e.g. OutOfMemoryError - resulting in a dead daemon) or similarly the JVM aborts (bug etc.).

In any case the attached patch goes slightly further and provides a '-restarts n' option which can be set to:
-1 (infinite, also the default and mirrors existing behaviour)
0 (one-shot mode) up to (MAX_INT-1) fixed restart count and specific to the platform.

The patch is just an example of how it could be done.
Note that the intention here is to limit the restart count for successive fatal errors - not for controlled restarts initiated by the administrator via a signal, which actually resets the counter


  was:
Our particular use-case requires that JSVC not automatically restart the daemon if the child process throws a fatal error (e.g. OutOfMemoryError - resulting in a dead daemon) or similarly the JVM aborts (bug etc.).

In any case the attached patch goes slightly further and provides a '-restarts n' option which can be set to:
-1 (infinite, also the default and mirrors existing behaviour)
0 (one-shot mode) up to (MAX_INT-1) fixed restart count and specific to the platform.

The patch is just an example of how it could be done.
Note that the intention here is to limit the restart count for successive fatal errors - not for controlled restarts initiated by the administrator via a signal.


> Specify a maximum limit for automatic restarts
> ----------------------------------------------
>
>                 Key: DAEMON-334
>                 URL: https://issues.apache.org/jira/browse/DAEMON-334
>             Project: Commons Daemon
>          Issue Type: Improvement
>          Components: Jsvc
>    Affects Versions: 1.0.16
>         Environment: Unix / Linux systems
>            Reporter: Brett Delle Grazie
>            Priority: Minor
>              Labels: newbie, patch
>         Attachments: 01-control-automatic-restarts.patch
>
>
> Our particular use-case requires that JSVC not automatically restart the daemon if the child process throws a fatal error (e.g. OutOfMemoryError - resulting in a dead daemon) or similarly the JVM aborts (bug etc.).
> In any case the attached patch goes slightly further and provides a '-restarts n' option which can be set to:
> -1 (infinite, also the default and mirrors existing behaviour)
> 0 (one-shot mode) up to (MAX_INT-1) fixed restart count and specific to the platform.
> The patch is just an example of how it could be done.
> Note that the intention here is to limit the restart count for successive fatal errors - not for controlled restarts initiated by the administrator via a signal, which actually resets the counter


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)