Mailing-List: contact dev-help@quarks.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@quarks.incubator.apache.org
Date: Tue, 5 Apr 2016 21:05:25 +0000 (UTC)
From: "Victor Dogaru (JIRA)" <jira@apache.org>
To: dev@quarks.incubator.apache.org
Message-ID: <JIRA.12948154.1457469695000.142904.1459890325502@Atlassian.JIRA>
In-Reply-To: <JIRA.12948154.1457469695000@Atlassian.JIRA>
References: <JIRA.12948154.1457469695000@Atlassian.JIRA>
 <JIRA.12948154.1457469695140@arcas>
Subject: [jira] [Commented] (QUARKS-13) Start over Quarks when Quarks
 crashes (Linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Victor Dogaru commented on QUARKS-13:
-------------------------------------

The YAJSW project provides wrappers to run a Java application as a Windows service or Unix daemon,
and restart it if the JVM has crashed. 

It has a list of additional features, including: 
 - Support for RunAs / sudo
 - Support for System Tray Icon for desktop messaging. Display tray messages from a groovy script, for example in case of exceptions.
 - Windows Cluster aware
 - Windows Session0 support
 - Support for Java Network Launch Protocol (JNLP)
 - Monitoring the JVM heap size and deadlocks

It used to have a GPL/LGPL license, but this has recently changed to an Apache license, together with core dependencies. According to http://yajsw.sourceforge.net/#mozTocId236130 there are still a few non-core dependencies with GPL/LGPL license. 

Maybe it's just a case of YAGNI, but I would try to investigate a simpler solution.
think that one can evaluate again if any of the extra functionality is needed.

> Start over Quarks when Quarks crashes (Linux)
> ---------------------------------------------
>
>                 Key: QUARKS-13
>                 URL: https://issues.apache.org/jira/browse/QUARKS-13
>             Project: Quarks
>          Issue Type: New Feature
>          Components: Runtime
>            Reporter: Victor Dogaru
>            Assignee: Victor Dogaru
>              Labels: failure-recovery
>
> Thinking of a mechanism which restarts the Quarks application if the JVM running Quarks hangs or closes unexpectedly. These options come to mind:
> - Write a script which checks for the pid of the jvm process running Quarks and restarts Quarks if the pid is not there. Run the script every minute using a cron job.
> - Setup Quarks app to run as a Linux service. Use inittab or systemd to manage Linux services and have options to restart a managed process automatically.
> There is also the hardware option. Embedded platforms frequently rely on watchdog hardware that resets it automatically if software stops periodically signalling the hardware that it is still alive.
> Anyone have any thoughts on this?


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