On 19/08/17 20:02, Nicholas Hagen wrote: <snip/>
> Is this the expected behavior now with Tomcat? If so, are there better > recommendations on how to have a general purpose health check wait until > the web applications are fully init'd? I do not see the behaviour you describe with the latest 8.5.x build. Neither am I aware of anything that has changed with the processing of load-on-startup that would have changed the behaviour between 7.0.x and 8.x. If I deploy the test application to a running instance, I get 404s for ServletA and ServletB while ServletA is processing the init call. This is as expected. The app deployment is not complete so the requests are routed to the default web application which returns the 404. If I perform the test during start-up, the user agent hangs on the request to ServletB until ServletA init completes, Tomcat starts and then the request is correctly processed. This looks to be an issue somewhere between your application and Spring Boot. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
