I'm running into a similar issue as this thread over on the Lucee forums: https://dev.lucee.org/t/loadcomponent-for-multiple-instances/3997/2 I have no idea why the error would be called, because I'm certainly not using the Lucee dialect anywhere within the code. The Quartz Scheduler stuff does run outside of a web context (at least in the background threads). Could that happen when

lucee.runtime.util.Creation.createComponentFromPath()

recieved

null

for an instance of the

PageContext

object?

When it starts to crash, check your IO usage. This usually is an issue the the disk being overtaxed and the swap of the machine being overworked.

There is no crashing, just random errors that show up in the log files. And it only sometimes fails. Some of the tasks in Quartz continue to run just fine. It appears to be a problem when a specific Quartz thread cannot create the page context any longer, then that thread becomes ripe with errors. Other threads will continue to work fine.