On Mon, Jun 8, 2009 at 12:50 PM, Jenny Brown<skywind@xxxxxxxxx> wrote: >> What you should really try, is to use the browser to access that same URL >> directly on Tomcat, without going through Apache, and see how long you have >> to wait there to get an answer after you start Tomcat. > > Hitting tomcat directly on port 8080 is very fast. That difference in > speed is what led me to believe that apache seemed to be caching. To clarify this a bit: In a single web browser, I can load http://www.myserver.com:8080/manager/html/ in tomcat and see results, and load http://www.myserver.com/manager/html/ in another window (routes through apache, then ajp to tomcat) and see 503 -- at the same time. That is, tomcat is up, the manager web app is answering requests, and I can interact with it normally, for a significant amount of time, while apache continues to say it can't get to it. Jenny Brown --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|