Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Fri, 23 Jun 2017 10:22:00 +0000 (UTC)
From: "Consultant Leon (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.13081974.1498184119000.90707.1498213320145@Atlassian.JIRA>
In-Reply-To: <JIRA.13081974.1498184119000@Atlassian.JIRA>
References: <JIRA.13081974.1498184119000@Atlassian.JIRA> <JIRA.13081974.1498184119940@jira-lw-us.apache.org>
Subject: [jira] [Updated] (DAEMON-366) Windows service fails to stop with
 error code 1053 (using Windows 7 service manager)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 23 Jun 2017 10:22:05 -0000


     [ https://issues.apache.org/jira/browse/DAEMON-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Consultant Leon updated DAEMON-366:
-----------------------------------
    Summary: Windows service fails to stop with error code 1053 (using Windows 7 service manager)  (was: CLONE - Windows service fails to stop with error code 1053 (using Windows 7 service manager))

> Windows service fails to stop with error code 1053 (using Windows 7 service manager)
> ------------------------------------------------------------------------------------
>
>                 Key: DAEMON-366
>                 URL: https://issues.apache.org/jira/browse/DAEMON-366
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Procrun
>    Affects Versions: 1.0.15
>         Environment: Windows 7 64bit - using 64-bit prunsrv.exe in jvm mode
> Using 64-bit Java JRE 1.8.0_73
>            Reporter: Consultant Leon
>            Assignee: Guillaume Chauvet
>              Labels: prunsrv, stop, windows
>
> Using Windows services manager (services.msc) to start/stop service.
> Service installed with the following start/stop settings.
> --StartMode=jvm --StartClass=com.myorg.MyClass --StartMethod=start 
> --StopMode=jvm --StopClass=com.myorg.MyClass --StopMethod=stop 
> Service starts OK.
> When I use services manager to stop the service, the application stops running but the prunsrv.exe process does not terminate.
> Eventually the services manager reports that:
> "Windows could not stop the <MyServiceName> service on Local Computer.  Error 1053: The service did not respond to the start or control request in a timely fashion."
> The service then stays at status "stopping" & cannot be restarted without first killing the prunsrv.exe process.
> Looking at the application logs I can see that the application's stop() method gets called - the final line in this method is a logging call which is executing OK.
> The commons-daemon-<date>.log file has the following entries:
> [2013-05-09 17:18:02] [info]  [10944] Commons Daemon procrun (1.0.15.0 32-bit) started
> [2013-05-09 17:18:02] [info]  [10944] Running '<MyServiceName>' Service...
> [2013-05-09 17:18:02] [info]  [ 9224] Starting service...
> [2013-05-09 17:18:11] [info]  [ 9224] Service started in 9202 ms.
> [2013-05-09 17:18:23] [info]  [10780] Stopping service...
> [2013-05-09 17:18:24] [info]  [10780] Service stop thread completed.
> This problem does not occur in daemon versions 11->14.
> I have only seen it in daemon-1.0.15


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)