Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Wed, 9 Dec 2015 15:56:10 +0000 (UTC)
From: "Johannes Meier (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12920473.1449676512000.314233.1449676570995@Atlassian.JIRA>
In-Reply-To: <JIRA.12920473.1449676512000@Atlassian.JIRA>
References: <JIRA.12920473.1449676512000@Atlassian.JIRA>
 <JIRA.12920473.1449676512601@arcas>
Subject: [jira] [Created] (DAEMON-342) Procrun does not support accuratly
 the service lifecycle states
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Johannes Meier created DAEMON-342:
-------------------------------------

             Summary: Procrun does not support accuratly the service lifecycle states
                 Key: DAEMON-342
                 URL: https://issues.apache.org/jira/browse/DAEMON-342
             Project: Commons Daemon
          Issue Type: Improvement
          Components: Procrun
    Affects Versions: 1.0.15
            Reporter: Johannes Meier
            Priority: Minor


It is not possible to show accurately the different states of a service.
A service has the states: starting, started, stopping , stopped
An example for the starting/started phase:
I can tell procrun which start method to use, maybe start().
Procrun starts my start() method and as written in the documentation the start method does not return until service has stopped.
Procrun does not know if my service has finished the starting period
it tells windows my service has started but it is still starting.
A second service which depends on the started service beliefs the service is already working now.


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