Just want to document the solution for folks facing the same problem in the future. Actually, it turned out to be quite nasty, in part because I wasn't paying much attention to the logs which were giving warnings that the AJP port was already bound. Being used to Tomcat failing to start when it hits a used port, I glazed over these warnings. Apparently, Tomcat will only fail to start when either the shutdown port or the http connector port are used, but will still continue with a warning if it can't bind a port for an AJP connector.
The problem was caused by another application, VMWare's web admin console, using port 8009 for it's own needs. The problem was compounded by the fact that VMWare installed an AJP listener on that port. That's why it was responding to Apache's inquiries, but with an error message. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
