I know this thread is really old, but I’m seeing the same problem.
We have some code that is running within Quartz Scheduler and we randomly see the same problem. Most of the time everything works fine, but eventually we will start seeing exception stacks like:
lucee.runtime.exp.ApplicationException: The Lucee dialect is disabled, to enable the dialect set the environment variable or system property "lucee.enable.dialect" to "true" or set the attribute "allow-lucee-dialect" to "true" with the "compiler" tag inside the lucee-server.xml.
at lucee.runtime.PageContextImpl.notSupported(PageContextImpl.java:1081)
at lucee.runtime.component.ComponentLoader._search(ComponentLoader.java:204)
at lucee.runtime.component.ComponentLoader._search(ComponentLoader.java:188)
at lucee.runtime.component.ComponentLoader.searchComponent(ComponentLoader.java:82)
at lucee.runtime.PageContextImpl.loadComponent(PageContextImpl.java:3280)
at lucee.runtime.op.CreationImpl.createComponentFromName(CreationImpl.java:298)
at lucee.runtime.op.CreationImpl.createComponentFromPath(CreationImpl.java:313)
Restarting the server seems to stop them for awhile.
Any idea why this error would be getting thrown seemingly at random?
I’m guessing that somewhere in the process something is not being closed that should be closed, but I’m not sure what. Trying to replicate the behavior has been difficult because the problem generally doesn’t start until the server has been running for an extended period (i.e. weeks/months).