Meta tags:
description=Hi everyone, We’ve been migrating our Docker builds to use Lucee 7’s native build-time warmup (LUCEE_ENABLE_WARMUP=true) combined with Server.cfc:onBuild() (introduced in LDEV-4922 ) to pre-cache Maven dependencies dec…;

Headings (most frequently used words):

docker, build, warmup, behaviour,

Text of the page (most frequently used words):
the (20), lucee (18), server (9), #warmup (8), light (8), with (7), run (7), lco (6), and (6), onbuild (6), cfc (6), engine (5), tomcat (5), pass (4), jar (4), build (4), first (3), for (3), loader (3), lucee_enable_warmup (3), true (3), docker (3), dev (3), until (2), dockerfile (2), use (2), full (2), pre (2), place (2), starts (2), ldev (2), thanks (2), this (2), never (2), second (2), start (2), september (2), 2026 (2), before (2), directly (2), core (2), startup (2), catalina (2), present (2), disk (2), not (2), lifecycle (2), container (2), opt (2), context (2), our (2), support (2), behaviour (2), powered, best, viewed, javascript, enabled, discourse, privacy, policy, terms, service, guidelines, categories, home, like, that, fixed, workarounds, are, twice, instead, matching, tracked, here, 6472, clear, write, agreed, bug, only, fetches, exits, runs, 14am, micstriit, npe, configimpl, clean, boot, when, event, gateways, auto, component, deployed, question, suggestion, users, authoring, slim, containers, running, two, expected, pattern, should, chain, into, once, extraction, finishes, during, bootstrap, contacts, downloads, unzips, bundles, terminates, invoked, consecutive, now, already, triggers, cfmlengineimpl, onstart, executes, cleanly, why, happens, cold, filesystem, responsible, fetching, patch, because, yet, initial, cfml, which, initializes, pagecontext, dispatches, does, exit, hook, shuts, down, felix, download, org, fresh, existing, state, containing, function, usr, local, bin, observation, steps, reproduce, own, starting, from, stock, apache, downloading, noticed, interesting, behavior, been, migrating, builds, native, time, combined, introduced, 4922, cache, maven, dependencies, declared, javasettings, mavenload, everyone, 34am, philsw,

Text of the page (random words):
docker build warmup behaviour support lucee dev lucee dev docker build warmup behaviour dev support philsw september 16 2026 2 34am 1 hi everyone we ve been migrating our docker builds to use lucee 7 s native build time warmup lucee_enable_warmup true combined with server cfc onbuild introduced in ldev 4922 to pre cache maven dependencies declared in javasettings mavenload we build our own tomcat container starting from stock apache tomcat and downloading lucee light 7 0 5 41 jar directly we noticed an interesting lifecycle behavior steps to reproduce fresh container with tomcat and lucee light 7 0 5 41 jar in lucee no existing opt lucee server lucee server state on disk place server cfc at opt lucee server lucee server context context server cfc containing an onbuild function run tomcat with lucee_enable_warmup true usr local tomcat bin catalina sh run observation on the first run the lucee light bootstrap loader contacts download lucee org downloads 7 0 5 41 lco unzips bundles and terminates server cfc onbuild is never invoked on a second consecutive run lucee_enable_warmup true catalina sh run 7 0 5 41 lco is now already present on disk the engine starts up triggers cfmlengineimpl onstart and server cfc onbuild executes cleanly why this happens on a cold filesystem with lucee light the loader is responsible for fetching the lco patch because the core engine is not yet present at initial startup the full cfml engine lifecycle which initializes pagecontext and dispatches onbuild does not run on pass 1 before the warmup exit hook shuts down felix question suggestion for users authoring slim containers with lucee light jar is running a two pass warmup in the dockerfile the expected pattern or should the lucee light loader chain directly into the core engine startup once lco extraction finishes during warmup thanks npe in configimpl on clean boot when event gateways auto start before component cfc is deployed micstriit september 24 2026 5 14am 2 thanks for the clear write up agreed this is a bug with lucee light the first warmup pass only fetches the lco and exits so onbuild never runs until a second start tracked here ldev 6472 until that s fixed workarounds are run warmup twice in the dockerfile use the full lucee jar instead of lucee light or pre place the matching lco so the first pass starts the engine 1 like home categories guidelines terms of service privacy policy powered by discourse best viewed with javascript enabled