https://bz.apache.org/bugzilla/show_bug.cgi?id=63389
--- Comment #5 from Christopher Schultz <ch...@christopherschultz.net> --- (In reply to Igal Sapir from comment #4) > (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. So if the servlet does something like downloading a bunch of files or whatever? I mean, the JVM stops, so reading db info into a cache or something doesn't help. Just making sure that this has nothing to do with Tomcat itself, which won't benefit at all. > > 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. Gotcha. I'm curious what the Lucee engine does on startup that happens ONE TIME instead of each time the application is launched. > > 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. So these are extensions for Lucee? > In monolith deployments that might have been acceptable, but in Docker or > server-less deployments it is not. I have to admit that I find "serverless servlets" an amusing construct. -- 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
