On 21/03/2013 13:06, Christopher Schultz wrote: > Mark, > > On 3/21/13 6:17 AM, Mark Thomas wrote: >> The connector is not started until all web applications have been >> started. That means that: - all loadOnStartup servlets have >> been loaded - all ServletContextListeners have completed - etc. > >> It also means that Tomcat has finished its internal startup for >> the Contexts, Host(s) and Engine. > >> There are no hooks (apart from receiving a request) for a web >> application to trigger any further initialisation so it must be >> ready to process requests at this point. > > When a webapp is reloaded, the connection will remain running with > no interruption, right? Requests to that webapp will stall until > the webapp is back up again?
Yes. They will he held by Tomcat until the web app is back up. > IIRC, it used to be that during a webapp reload, you might get > weird responses either from Tomcat or the ROOT webapp (it might > have been because I was running without a ROOT webapp, which I have > since fixed). That was mostly likely one of the bugs in this area that got fixed. > What about the case of re-deployment? Does it behave just like a > reload? No. You'll get 404s. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
