https://bz.apache.org/bugzilla/show_bug.cgi?id=63389
--- Comment #4 from Igal Sapir <isa...@apache.org> --- (In reply to Christopher Schultz from comment #3) > 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. This is not for creating the Tomcat directory structure, but all of the initialization of the servlet itself. > 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? This is not a JSP per-se, even though it follows the JSP interface. In this case it is the Lucee Application Server that implements a CFML engine. > 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. The Application Server can take a while on first run because according to configuration settings it might download extensions and install them, etc. Without downloading extensions it takes about 3.5s to launch on my latptop. With extensions it can take up to 60s. In monolith deployments that might have been acceptable, but in Docker or server-less deployments it is not. You can find more information in the Lucee ticket system [1], where I actually resolved the issue for Lucee but it feels like a hack and would be much better if resolved on the Tomcat level as 1) it will be cleaner, and 2) it will help other projects who might need this feature. [1] https://luceeserver.atlassian.net/browse/LDEV-1196 -- 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
