Return-Path: X-Original-To: apmail-quarks-dev-archive@minotaur.apache.org Delivered-To: apmail-quarks-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 533FB183BA for ; Mon, 4 Apr 2016 19:54:28 +0000 (UTC) Received: (qmail 9090 invoked by uid 500); 4 Apr 2016 19:54:28 -0000 Delivered-To: apmail-quarks-dev-archive@quarks.apache.org Received: (qmail 9068 invoked by uid 500); 4 Apr 2016 19:54:28 -0000 Mailing-List: contact dev-help@quarks.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@quarks.incubator.apache.org Delivered-To: mailing list dev@quarks.incubator.apache.org Received: (qmail 9057 invoked by uid 99); 4 Apr 2016 19:54:28 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Apr 2016 19:54:28 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D67E51A463D for ; Mon, 4 Apr 2016 19:54:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.021 X-Spam-Level: X-Spam-Status: No, score=-4.021 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 2JiPEKb2Ggob for ; Mon, 4 Apr 2016 19:54:27 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with SMTP id 900F85FAFB for ; Mon, 4 Apr 2016 19:54:26 +0000 (UTC) Received: (qmail 7868 invoked by uid 99); 4 Apr 2016 19:54:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Apr 2016 19:54:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B95662C1F5A for ; Mon, 4 Apr 2016 19:54:25 +0000 (UTC) Date: Mon, 4 Apr 2016 19:54:25 +0000 (UTC) From: "Victor Dogaru (JIRA)" To: dev@quarks.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (QUARKS-13) Start over Quarks when Quarks crashes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/QUARKS-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Victor Dogaru reassigned QUARKS-13: ----------------------------------- Assignee: Victor Dogaru > Start over Quarks when Quarks crashes > ------------------------------------- > > 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)