[ 
https://issues.apache.org/jira/browse/DAEMON-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072418#comment-16072418
 ] 

Raghavaraju Kudari edited comment on DAEMON-361 at 7/4/17 11:24 AM:
--------------------------------------------------------------------

Hi 

Thanks for the Response.

Yes. Tomcat Bootstrap.java  is successfully stopping the tomcat  by sending OS 
signal. So it is stopped and even the associated process "myappserver.exe" got 
killed. However in windows Services  I am seeing an Alert  as mentioned below 

Windows Could not stop the "myappserver service" service on Local Computer.  

Error 1 : Incorrect function.

Attached screen shot.

Regards
Veeru




was (Author: raghavaraju.k):
Hi 

Thanks for the Response.

Yes. Tomcat Bootstrap.java  is successfully stopping the tomcat  by sending OS 
signal. So it is stopped and even the associated process "myappserver.exe" got 
killed. However in windows Services  I am seeing an Alert  as mentioned below 

Windows Could not stop the "myappserver service" service on Local Computer.  

Error 1 : Incorrect function.



Regards
Veeru



> Windows service fails to stop with error code 1053 (using Windows service 
> manager)
> ----------------------------------------------------------------------------------
>
>                 Key: DAEMON-361
>                 URL: https://issues.apache.org/jira/browse/DAEMON-361
>             Project: Commons Daemon
>          Issue Type: Bug
>         Environment: windows 7/8/10
>            Reporter: Raghavaraju Kudari
>            Assignee: Bernd Eckenfels
>         Attachments: errormessage_winservices.png, error.png
>
>
> We are using windows service to start and stop our application.
> It is starting but not stopping and giving "{color:red}Error 1053 : "The 
> service did not respond to start or control request in a timely 
> fashion{color}" 
> To create windows service entry we used WinRun4J API and using catalina.jar 
> startup classes
> (org.apache.catalina.startup.Bootstrap) to perform this operation.
> It was worked earlier when we used tomcat 7 and started facing the issue 
> after we upgraded to tomcat 8.5



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

Reply via email to