On 10/05/2023 22:06, Gilles Maurice wrote:
Hello,
Our product currently uses Tomcat 8.5.83. We wanted to upgrade to Tomcat
8.5.88 but our product fails to start up with this version.
From my research I was able to determine the following facts:
- Upgrade to 8.5.84 works fine
- Upgrade to 8.5.85+ fails
- Our product uses "tomcat8.exe //US/vlm" to update the service
parameters (vlm is the internal name of our product)
- with 8.5.85, calling the following command works fine: tomcat8.exe
//US/vlm --Description myDescription
- setting java parameters don't work however, for example this command
fails: tomcat8.exe //US/vlm --JvmMs 128
- when running the command above, tomcat8.exe does not display an error
but the service is not updated
- the documentation at
https://tomcat.apache.org/tomcat-8.5-doc/windows-service-howto.html
indicates that the java update parameters are not set when in exe mode
but ours is in jvm mode. For example, the following command will not set
the JvmMs value: tomcat8.exe //US/vlm --Jvm auto --StartMode jvm
--StopMode jvm --JvmMs 128
Does anyone have any info on how to get around this?
I am unable to recreate the problem described.
tomcat8.exe //US/Tomcat8 --JvmMs 128
works for me with a clean Tomcat installation.
How are you determining if the service is updated?
Otherwise, can someone direct me to the source code for tomcat8.exe so I
can see if I can find the cause of this issue myself?
You want Commons Daemon. Tomcat 8.5.85 upgraded from 1.3.2 to 1.3.3.
https://github.com/apache/commons-daemon
Tomcat8.exe is a renamed prunsrv.exe
Tomcat8w.exe is a renamed prunmgr.exe
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
