On Wed, Oct 19, 2011 at 10:48, André Warnier <a...@ice-sa.com> wrote: > Hi. > > The problem can also be due just to the difference in startup time between > Apache httpd and Tomcat. At the time Apache httpd (and its embedded > mod_proxy_ajp module) try to contact Tomcat, Tomcat has possibly not yet > "opened" its Connector on port 8009, which causes the host to refuse a > connection to that port. > > In my experience anything involving Java tends to take a while to "start the > machinery" (it is after all a "java virtual machine"). > In the practice thus, what we always do in such configurations, is to start > Tomcat first (which really means mostly "start the java virtual machine > which runs Tomcat") > , wait a couple of seconds, and then start the Apache httpd part. >
Actually, there is a reliable way of waiting for Tomcat to be fully started: wait to see the port specified in <Server> open for listening. Then you are sure Tomcat is fully loaded. This is what I use and it's very reliable. -- Francis Galiegue ONE2TEAM Ingénieur système Mob : +33 (0) 683 877 875 Tel : +33 (0) 178 945 552 f...@one2team.com 40 avenue Raymond Poincaré 75116 Paris --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
