Bug 63285 - service.bat does not handle changed "Windows Service Name" defined during Tomcat Windows Installation
Summary: service.bat does not handle changed "Windows Service Name" defined during Tom...
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 8
Classification: Unclassified
Component: Packaging (show other bugs)
Version: 8.5.39
Hardware: PC All
: P2 normal (vote)
Target Milestone: ----
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-25 10:46 UTC by bk
Modified: 2019-08-08 12:41 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bk 2019-03-25 10:46:02 UTC
Pleas enable service.bat to deal with a changed "Windows Service Name" defined during Tomcat Windows Installation.

During the Apache Tomcat 8 Setup You can define on the "Configuration Options" page a "Windows Service Name". If you change the default "Tomcat8" this results not only in a changed installation folder and a changed Windows Service Name, but also to renamed files bin/Tomcat8.exe and bin/Tomcat8w.exe ('Windows service wrapper executables').

The proposed changes of Pull Request 139 https://github.com/apache/tomcat/pull/139 deal with such a renamed Windows service wrapper executables by using the provided parameter name for the service name. Note that the parameter is no longer optional then!

Another solution would be to change the Windows installer (NSI) and do not rename the bin/Tomcat@VERSION_MAJOR@.exe and bin/Tomcat@VERSION_MAJOR@w.exe during installation.
Comment 1 Mark Thomas 2019-08-08 12:41:59 UTC
Fixed in:
- master for 9.0.23 onwards
- 8.5.x for 8.5.44 onwards
- 7.0.x for 7.0.97 onwards