Matthew Woodward said the following on 08/31/2010 01:18 PM: > > Now what COULD be happening is if you're using AJP proxying, that > leave a connection open between Tomcat and Apache. So if you're not > actually *killing* the Tomcat process (meaning kill -9 pid vs. just > running shutdown.sh), then shutdown.sh might look like it worked when > actually it didn't. > If I kill Tomcat, I always have to restart Apache. Also, running shutdown.sh take a while (20-30 seconds) depending on the number of applications as Tomcat runs destroy on a bunch of objects. Usually, I just kill Tomcat and restart then restart Apache. I do this enough that I wrote a script.
If you don't restart Apache, AJP appears to hold on to some pipes to an instance of Tomcat that doesn't exist. That's usually where you see that you can surf to localhost:8080 but not mywebsite:80 and see it via the proxying. HTH, .Peter -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon official manual: http://www.openbluedragon.org/manual/ Ready2Run CFML http://www.openbluedragon.org/openbdjam/ mailing list - http://groups.google.com/group/openbd?hl=en
