At $work, we have an automated build system that twice-daily compiles our application and deploys it to the Tomcat servers in our QA environment. It uses the Tomcat manager web service (and the Tomcat Ant tasks) to manage this behavior. More precisely, it first builds the application, then undeploys the old application, then shuts down Tomcat, then runs database upgrades against the QA database, then starts Tomcat back up, and then finally deploys the application.
We've been having a problem with random FileNotFoundExceptions whenever the Ant task tries to deploy the WAR file using the Tomcat manager web service, and we recently figured out what's going on. If the only application that's running on Tomcat is our application, we don't have any problems. However, if there are other applications, sometimes those applications start before the manager application starts. Sometimes those applications take /several minutes/ to start before the manager starts. However, the order they appear in appears to be random. We can start Tomcat and immediately go to the manager, then shut down Tomcat, start it back up with the same application, and it suddenly be 2-3 minutes before the manager is available. The FileNotFoundExceptions in our Ant build happen when the Ant task successfully contacts Tomcat but Tomcat returns a 404 for the manager because that application hasn't started yet. That's unpleasant. So, is there a way to make the manager application or applications always be the first ones loaded? We really need the Tomcat-supplied manager applications to start first so that we can consistently automatically deploy our applications. Nick --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
