2014-02-28 23:00 GMT+04:00 Jeffrey Janner <jeffrey.jan...@polydyne.com>: > While working through a migration, I discovered something interesting. > Apparently you don't need any working connectors for a functioning (?) Tomcat > instance. > Setup: Tomcat 7.0.51, Java 1.7.0_51, Windows 2008 R2 64-bit > Config had only two <Connectors> both with the address= and port= parameters > set. > I had yet to add the referenced IP address to any network adapter when I > started the Tomcat service. > The service came up, logged the failure to bind to the address/port > assignments, and then deployed the webapps. > So I had a functional application running, but no way to connect to test > against it. > I suppose one would expect this to happen, and I don't know if a lack of > running connectors could be detected and a shutdown instituted, but it just > seemed a little odd.
This behaviour is configurable via a system property. The default behaviour is to let Tomcat to start up, because of 1. backwards compatibility concerns, 2. you can connect via JMX and configure/start/stop connectors as necessary. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
