On Tue, Aug 31, 2010 at 10:27 AM, Alan Holden <[email protected]> wrote:
> But if I've already browsed the application using one method, AND then try > to browse it again via the other one, Tomcat tries to start a fresh process > or something, sees the port conflict, throws a ton of exceptions and freezes > everyone. > I kinda doubt that's what's happening--I do that all the time. You mean if you browse to http://server:8080/whatever and then do http://server/whatever this occurs? I do that pretty frequently and haven't seen it spawn a new tomcat process. There's nothing in how the proxying works that would tell it to do that. 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. -- Matthew Woodward [email protected] http://blog.mattwoodward.com identi.ca / Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html -- 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
