> -----Original Message----- > From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] > Sent: Wednesday, June 05, 2013 8:04 AM > To: Tomcat Users List > Subject: RE: Tomcat 6 and Windows Service > > > From: walter.heesterm...@toyota-europe.com > > [mailto:walter.heesterm...@toyota-europe.com] > > Subject: RE: Tomcat 6 and Windows Service > > > I can set the following Java options > > > -Dcom.sun.management.jmxremote.port=10150 > > > The stop using shudown class is > org.apache.catalina.startup.Bootstrap > > with argument stop, stays hanging because the java process to stop > the > > service tries to connect port 10150; > > Initiating a stop creates another process which uses all of the options > specified, thus creating the port conflict you're seeing. If you > configure the ports using the JMX listener, only the server process > will use them. > > http://tomcat.apache.org/tomcat-6.0- > doc/config/listeners.html#JMX_Remote_Lifecycle_Listener_- > _org.apache.catalina.mbeans.JmxRemoteLifecycleListener > > You can also stop Tomcat by sending the process an appropriate signal, > or running the shutdown.bat script (even when Tomcat is running as a > service). >
The shutdown.bat script won't work if you set the shutdown port to "-1". This appears to be the recommended practice for running as a Windows service, as it really isn't needed and limits the ability of a rogue user (non-admin) to shutdown the Tomcat service. Under Windows, you should really just use either the Services control panel, net start/stop at the command line, or the Monitor Tomcat application. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
