[
https://issues.apache.org/jira/browse/DAEMON-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16060327#comment-16060327
]
Consultant Leon commented on DAEMON-366:
----------------------------------------
as with all other reporters confirming this bug it's exactly as stated and easy
to reproduce for me.
The moment we upgraded to a > 1.0.14 tomcat8.exe or tomcat7.exe from a tomcat >
7.0.39 , the shutdown of the service failed.
The java process terminated nicely and the console reports thread ended but
tomcat7/8 .exe remains running.
[2017-06-23 04:18:27] [info] [ 9392] Commons Daemon procrun (1.0.15.0 64-bit)
started
[2017-06-23 04:18:27] [info] [ 9392] Running 'HelloWorld6' Service...
[2017-06-23 04:18:27] [info] [ 1500] Starting service...
[2017-06-23 04:18:28] [info] [ 1500] Service started in 1270 ms.
[2017-06-23 04:18:36] [info] [12796] Stopping service...
[2017-06-23 04:18:37] [info] [12796] Service stop thread completed.
... D:\application\bin\win\AMD64
$ sc queryex HelloWorld6
SERVICE_NAME: HelloWorld6
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
PID : 0
FLAGS :
... D:\application\bin\win\AMD64
$ sc start HelloWorld6
SERVICE_NAME: HelloWorld6
TYPE : 10 WIN32_OWN_PROCESS
STATE : 2 START_PENDING
(NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x7d0
PID : 11384
FLAGS :
... D:\application\bin\win\AMD64
$ sc queryex HelloWorld6
SERVICE_NAME: HelloWorld6
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
PID : 11384
FLAGS :
... D:\application\bin\win\AMD64
$ sc stop HelloWorld6
SERVICE_NAME: HelloWorld6
TYPE : 10 WIN32_OWN_PROCESS
STATE : 3 STOP_PENDING
(NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x2
WAIT_HINT : 0xbb8
... D:\application\bin\win\AMD64
$ sc queryex HelloWorld6
SERVICE_NAME: HelloWorld6
TYPE : 10 WIN32_OWN_PROCESS
STATE : 3 STOP_PENDING
(NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x3
WAIT_HINT : 0x493e0
PID : 11384
FLAGS :
... D:\application\bin\win\AMD64
$ sc queryex HelloWorld6
SERVICE_NAME: HelloWorld6
TYPE : 10 WIN32_OWN_PROCESS
STATE : 3 STOP_PENDING
(NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x3
WAIT_HINT : 0x493e0
PID : 11384
FLAGS :
> CLONE - 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 32-bit prunsrv.exe in jvm mode
> Using 32-bit Java JRE 1.7.0_17
> 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)
