Thanks for your reply Chris. I mentioned in one of the replies that this is only a question regarding why an app in the initialization phase should or should not make an HTTP call, for whatever reason, to a "yet to be initialized" context in the same container. This is a case of "I want to run the whole production system on my dev machine." There are unexpected issues like this that a code fix won't/can't solve.
Everything works fine in the production setting where apps are physically separated and consideration of startup order is possible. I am able to run a Virtualized environment on my dev machine, so it isn't that I don't have a solution, just a curiosity as to what is happening under the Tomcat covers during this scenario. -Scot --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
