Jira Core: Windows service won't start - error 1053

Question

Hello.

From time to time (every 1-2 weeks) the Windows service for my Jira Core installation won't start anymore and shows the error "Windows could not start the Atlassian JIRA service on Local Computer. Error 1053: the service did not respond to the start or control request in a timely fashion". The error is thrown immediately after hitting the start button of the service.

Only workaround for now is to delete the service, restart the server and setting up the service again. But this is no viable solution for a server that is intended to run 24/7.

Does anybody know a permanent solution for this problem? The server runs Windows Server 2012 R2 Standard (6.3.9600 Build 9600)

Jakub Sławiński · Answer

And what is in the logs when the service cannot start?

What you shared are logs from stopping the service or the irrelevant warnings.

Björn Bittins · Answer

There are only 2 line immediately before:

16-Jul-2019 02:21:50.348 INFO [Thread-249] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-8080"]
16-Jul-2019 02:21:50.395 INFO [Thread-249] org.apache.catalina.core.StandardService.stopInternal Stopping service [Catalina]

and 8h before that:

15-Jul-2019 18:07:28.127 WARNING [http-nio-8080-exec-16] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://tools.xyz.com/support/rest/issueNav/1/issueTable, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.
15-Jul-2019 18:07:28.268 WARNING [http-nio-8080-exec-25] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://tools.xyz.com/support/rest/issueNav/1/issueTable/stable, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.

Jakub Sławiński · Answer

This is too late - you should look at the earlier logs (i.e. few lines above).