edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QUARKS-13) Start over Quarks when Quarks crashes (Linux)
Date Fri, 08 Apr 2016 15:38:25 GMT

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

ASF GitHub Bot commented on QUARKS-13:

Github user ddebrunner commented on a diff in the pull request:

    --- Diff: scripts/cron/startapp.sh ---
    @@ -0,0 +1,119 @@
    +# Licensed to the Apache Software Foundation (ASF) under one or more
    +# contributor license agreements.  See the NOTICE file distributed with
    +# this work for additional information regarding copyright ownership.
    +# The ASF licenses this file to You under the Apache License, Version 2.0
    +# (the "License"); you may not use this file except in compliance with
    +# the License.  You may obtain a copy of the License at
    +#    http://www.apache.org/licenses/LICENSE-2.0
    +# Unless required by applicable law or agreed to in writing, software
    +# distributed under the License is distributed on an "AS IS" BASIS,
    +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    +# See the License for the specific language governing permissions and
    +# limitations under the License.
    +[ ! -n "${QUARKS:-}" ] && QUARKS=../..
    +# Application name identifies the running process.  For the scope of this
    --- End diff --
    Seems like with minor changes this could change from a sample to a reusable script, e.g.
passing in the classpath and main class name.

> 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

View raw message