commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghavaraju Kudari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DAEMON-361) Windows service fails to stop with error code 1053 (using Windows service manager)
Date Wed, 21 Jun 2017 03:24:00 GMT

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

Raghavaraju Kudari commented on DAEMON-361:
-------------------------------------------

Hi Bernd,

Thanks for the response. 
But issue is not with WinRun4J. I just specified that to explain the issue, which we are facing.
We are using "catalina.jar" startup API which resides in tomcat application, to start and
stop tomcat server . The issue is very much similar to  DAEMON-298. If this is wrong place
to create this ticket, please let us know where we can place this issue?


> 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
>         Attachments: 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)

Mime
View raw message