Jenny Brown wrote: ...Just to get better answers, can you provide some additional information, such as
- which Apache are you talking about (version) ? - which Tomcat (version) ? - how are they connected (connector ?) - on which platform (OS) ?Then anyway, as far as I know, /nothing/ is caching error messages. In other words, if you get an error message, it means that some component really tries to get an answer from Tomcat, and is not getting any yet.
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. In the Tomcat "server.xml", there is a <Connector> element for the direct HTTP port of Tomcat (probably on port 8080, or 8180). Note that port number. Then try to point your browser directly to that port, with the same URL as you would use through Apache.
In other words, if your normal URL is http://myhost.mycompany.com/myapp then try http://myhost.mycompany.com:8080/myappAgain in other words, when Tomcat tells you in its logfile that it is started, it means that Tomcat itself is started. But it does not necessarily mean that all the /applications/ that run under Tomcat are ready to answer requests. That may take quite a bit longer. Some applications may only get loaded and/or compiled when you call them for the first time.
--------------------------------------------------------------------- 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
|