2011/2/21 Dave Shevett <shev...@homeport.org>: > Hi folks, I have a relatively complex installation that I'm trying to > get the manager app deployed into. This was working at some point, but > now I can't seem to get anything but 400 errors out of it.
Tomcat respond with error 400 when it cannot map request to a valid web application (and thus feels desperate). One notorious case of it is when there is no ROOT webapp on a host: instead of error 404 you will receive zero-length response with HTTP response code of 400. >From a comment in your server.xml you know that you are missing the ROOT >webapp: <!-- (...) All vhosts except congov2 are working properly The difference is they have ROOT.xml files, and congov2 does not --> Do you have ROOT.xml on your default host (the "localhost" in your configuration) as well? > REDACTED.com:80 172.16.1.1 - - [21/Feb/2011:12:29:38 -0500] "PUT > /manager/deploy?path=%2Fcongo&war=&update=true HTTP/1.0" 400 - "-" > "Tomcat Maven Plugin/1.1" The above is an HTTP/1.0 request. I wonder whether it is mapped to a virtual host correctly or whether it is served by localhost instead (that depends on what is actually sent to Tomcat, though I see REDACTED.com in the above log line). You say that you have manager.xml deployed on that host, but is it actually running? (autodeploy is off on your host, so Tomcat won't notice the new webapp, unless you restart it, or tell it through API or JMX like the manager app does). Is the manager webapp starting up mentioned in the logs when Tomcat starts up? Is that manager.xml file readable by the user that runs Tomcat? Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
