https://bz.apache.org/bugzilla/show_bug.cgi?id=63389
--- Comment #3 from Christopher Schultz <ch...@christopherschultz.net> --- I'm definitely missing something, here. Launching Tomcat and then shutting it down saves zero time on the next launch except maybe to create a directory or two and unpack any WAR archives being deployed. If you want to warm the application, you'll want to pre-compile all the JSPs either using jspc or by just spamming the application with web requests. So what exactly is the point, here? I can see use-cases for building something like this (some people want to know when Tomcat is "really started"), but for triggering a shutdown to "warm" an app server? I don't get it. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
