Thanks do much for the quick reply, your response set me in the right direction to help diagnose the issue further.
In case you or others are interested here is the description of the issue and the workaround... As of Tomcat 8.5.85, when setting jvm parameters, tomcat8.exe is validating if the default --LogPath of %SystemRoot%\System32\LogFiles\Apache is accessible for read/write. In our test environment this is not the case. To make matters worse, our installer did not display the error message generated by tomcat8 so it made diagnosing the issue more difficult. The workaround was to simply set a --LogPath to a folder that we know is read/write. Thanks again for your help, Gilles ________________________________ From: Mark Thomas <ma...@apache.org> Sent: Thursday, May 11, 2023 8:50 AM To: users@tomcat.apache.org <users@tomcat.apache.org> Subject: Re: Setting service parameters not work in Tomcat 8.5.85+ [EXTERNAL] This email originated from outside of the organization. Do not click links or open attachments unless you recognize and trust the sender's email address. [You don't often get email from ma...@apache.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftomcat.apache.org%2Ftomcat-8.5-doc%2Fwindows-service-howto.html&data=05%7C01%7Cgilles.maurice%40snowsoftware.com%7C98892c73af2f4fd9325608db521eab50%7Cd76c28a10b62484998fd8cf2516370ce%7C0%7C0%7C638194063892271630%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=g%2F0iQIGr72QQi8ysUznER16PuIKrXAKWnrr8qkKQTZM%3D&reserved=0<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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fcommons-daemon&data=05%7C01%7Cgilles.maurice%40snowsoftware.com%7C98892c73af2f4fd9325608db521eab50%7Cd76c28a10b62484998fd8cf2516370ce%7C0%7C0%7C638194063892271630%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9bQdJRbAebm3W5yFc4kCR9%2B5bVs47l8KrCIZVgjzHTk%3D&reserved=0<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
