DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=30572>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30572 tomcat startup mode paramater ignored Summary: tomcat startup mode paramater ignored Product: Commons Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Daemon AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I'm using tomcat 5.0.27 (not sure which version of commons-daemon it is using underneath), and am encountering a problem when I try to install it as a service under windows 2003. The "--Startup auto" parameter seems to get ignored. The service gets installed, but is in "manual" mode, not "auto" mode as intended. Note that we were previously using tomcat 5.0.16 and have recently migrated to 5.0.27. There were a number of tweaks I had to make to the syntax we use to install tomcat as a service, to get it to work at all with 5.0.27. Below is a copy of the .bat script I am using to test service installation under 5.0.27: ------------------------------------------------------------------------------ set INSTALL_DIR=D:\Program Files\Emprisa Networks\E-NetAware set DATA_DIR=D:\E-netAware-data set TOMCAT_DIR=%INSTALL_DIR%\tomcat set TOMCAT_BIN=%TOMCAT_DIR%\bin set TOMCAT_LOG=%TOMCAT_DIR%\logs set TOMCAT_TMP=%TOMCAT_DIR%\temp set JVM_DIR=%INSTALL_DIR%\_jvm set JVM_BIN=%JVM_DIR%\bin set JVM_CLIENT=%JVM_BIN%\client set BOOTSTRAP_CLASS=org.apache.catalina.startup.Bootstrap set SERVICE_NAME=ENetAwareTomcat set DISPLAY_NAME=E-NetAware Web Service set DESCRIPTION=E-NetAware Tomcat Web Server - http://www.emprisanetworks.com "%TOMCAT_BIN%\tomcat5.exe" //IS//%SERVICE_NAME% --DisplayName "% DISPLAY_NAME%" --Description "%DESCRIPTION%" --Startup auto --Install "% TOMCAT_BIN%\tomcat5.exe" --Classpath "%TOMCAT_BIN%\bootstrap.jar" --StartClass %BOOTSTRAP_CLASS% --StopClass %BOOTSTRAP_CLASS% --StartParams start -- StopParams stop --Jvm "%JVM_CLIENT%\jvm.dll" --StdOutput "%TOMCAT_LOG% \stdout.log" --StdError "%TOMCAT_LOG%\stderr.log" --JvmOptions "- Dcatalina.base=%TOMCAT_DIR%;-Dcatalina.home=%TOMCAT_DIR%;-Djava.endorsed.dirs=% TOMCAT_DIR%\common\endorsed;-Duser.home=%DATA_DIR%;- Djava.util.logging.config.file=%DATA_DIR%\logging.properties;-Djava.io.tmpdir=% TOMCAT_TMP%" --JvmMx 512 --JvmMs 256 --StartMode jvm --StopMode jvm ------------------------------------------------------------------------------- The service seems to be installed correctly otherwise (e.g. tomcat serves up our application fine, once you manually start the service). I looked at the latest source code for commons-daemon and I don't see any reason why it would be ignoring the "--Startup auto" parameter. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
