The webapp won't service the requests, because it is "unavailable", until setAvailable(true) is called at the end of its start().
Connectors are start()'ed after the Engine, and thus after all the webapps. 2011/2/14 Shaun Farrugia <sfarru...@fry.com>: > I'm not asking if they will or will not be loaded. I am wondering if http > requests to a JSP page are blocked before the servlets are loaded. > > > > -----Original Message----- > From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] > Sent: Monday, February 14, 2011 12:14 PM > To: Tomcat Users List > Subject: Re: Tomcat 5.5.28 Servlet Spec 2.3 - When does Tomcat actually > service requests? > > 2011/2/14 Shaun Farrugia <sfarru...@fry.com>: >> I would think the same but I'm wondering that Tomcat is doing. Would it >> allow http requests to a JSP to be serviced before ALL of the servlets >> marked as load-on-startup are loaded? >> > > They will be loaded, but any failure will just mark this specific servlet as > unavailable and not webapp as a whole. > > See loadOnStartup(..) and setAvailable(true) calls in StandardContext#start() > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
