commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DAEMON-334) Specify a maximum limit for automatic restarts
Date Thu, 02 Nov 2017 13:11:01 GMT

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

Mark Thomas resolved DAEMON-334.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1

Many thanks for the patch.

> 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
>             Fix For: 1.1
>
>         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.4.14#64029)

Mime
View raw message