Bug 37785 - Changing startup type via Tomcat Monitor does not affect the service startup type
Summary: Changing startup type via Tomcat Monitor does not affect the service startup ...
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Native:Integration (show other bugs)
Version: 5.5.13
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-05 10:29 UTC by Dominik Drzewiecki
Modified: 2009-06-12 16:44 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dominik Drzewiecki 2005-12-05 10:29:45 UTC 
I started observing this behaviour in the 5.5.12 (or even earlier, I can't
remember). It might be related to procrun update which AFAIR took place some
time ago, as the downgrade to the tomcat5.exe and tomcat5w.exe provided with the
5.0.28 seems to fix the problem.
Comment 1 Dominik Drzewiecki 2005-12-05 11:09:01 UTC 
Did some more investigation and revealed that manually performing any of the
following commands (please observe the case diffs) *does* influence the service
startup type:

tomcat5.exe //US// --Startup auto
tomcat5.exe //US//tomcat5 --Startup auto
tomcat5.exe //US//Tomcat5 --Startup auto
tomcat5.exe //US//ToMcAT5 --Startup auto

HTH

I'd change the Product/component to Commons/Daemon respectively, but this bug
seems to me to be tomcat-related. Besides, tomcat bugs seem to be much better
monitored ;).
Comment 2 Yoav Shapira 2006-12-24 09:07:46 UTC 
Dominic, is this still an issue in your environment when using Tomcat 5.5.20?
Comment 3 Dominik Drzewiecki 2006-12-25 15:27:53 UTC 
Yep, the issue persists in 5.5.20 :/
Comment 4 Mark Thomas 2009-06-12 16:44:12 UTC 
I haven't checked earlier versions but the recently updated procrun that will ship with 5.5.28 works correctly.