Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 06B86DC9F for ; Mon, 12 Nov 2012 16:23:16 +0000 (UTC) Received: (qmail 69230 invoked by uid 500); 12 Nov 2012 16:23:15 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 68588 invoked by uid 500); 12 Nov 2012 16:23:14 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 68443 invoked by uid 99); 12 Nov 2012 16:23:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Nov 2012 16:23:14 +0000 Date: Mon, 12 Nov 2012 16:23:14 +0000 (UTC) From: "Jonathan Grimm (JIRA)" To: issues@commons.apache.org Message-ID: <1894716374.101170.1352737394125.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (DAEMON-267) prunsrv failure doesn't trigger windows service recovery actions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jonathan Grimm created DAEMON-267: ------------------------------------- Summary: prunsrv failure doesn't trigger windows service recovery actions Key: DAEMON-267 URL: https://issues.apache.org/jira/browse/DAEMON-267 Project: Commons Daemon Issue Type: Bug Components: Procrun Affects Versions: 1.0.10 Environment: Windows Reporter: Jonathan Grimm This is directly related to DAEMON-244, which goes a long way towards solving the problem but still doesn't trigger Windows Service recovery actions correctly. With that fix applied, when the Java process terminates abnormally prunsrv reports to the Windows Service Controller that the service had terminated and passes along the non-zero exit code from the app. However, actually notifying the service controller that the service has terminated at all (even with a non-zero exit code) prevents the recovery actions from kicking in. >From http://msdn.microsoft.com/en-us/library/ms685939(VS.85).aspx: "A service is considered failed when it terminates without reporting a status of SERVICE_STOPPED to the service controller" In order for the recovery actions to kick in, prunsrv should not notify the service controller at all when a failure is detected and should simply exit with a non-zero exit code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira