[jira] [Commented] (DAEMON-243) Support for Failure Recovery

["Marat Abrarov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DAEMON-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180559#comment-17180559 ] 

Marat Abrarov commented on DAEMON-243:
--------------------------------------

[~markt],

Sorry for the late reply. I don't think it really matters at the moment (at least for my case), but here is the thing I had to notice long ago:
 # WildFly project still uses 1.0.15 version of Apache Commons Daemon. I've just checked the latest - 20.0.1.Final - version.
 # My pull request was created from trunk (which looks far ahead of COMMONS_DAEMON_1_0_15 tag) but changes (diff I attached) should be applicable for 1.0.15 version.
 # I think it's responsibility of WildFly project to take care of this improvement and I believe that WildFly project is better to migrate to the latest version of Apache Commons Daemon instead of taking care of any patches / custom builds. I'll take a look if I can report anything (reproduce / test & report) to WildFly project soon.

Thank you for your feedback and work!

> Support for Failure Recovery
> ----------------------------
>
>                 Key: DAEMON-243
>                 URL: https://issues.apache.org/jira/browse/DAEMON-243
>             Project: Commons Daemon
>          Issue Type: New Feature
>          Components: Procrun
>    Affects Versions: 1.0.10
>         Environment: MS Windows
>            Reporter: Peter Ehrbar
>            Priority: Minor
>             Fix For: 1.1.0
>
>         Attachments: fail_without_stopped_status.diff
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The MS Windows Service Controller provides functionality to perform some basic failure recovery actions: Restart service or execute any command or restart the machine. This can be configured using the Service Controller GUI or in a shell with SC.EXE (commands FAILURE and FAILUREFLAG).
> It would be convenient if this could be configured also using procrun.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)