Details
Assignee
UnassignedUnassignedReporter
Michael SpragueMichael SpraguePriority
MajorNew Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Affects versions
Details
Details
Assignee
Unassigned
UnassignedReporter
Michael Sprague
Michael SpraguePriority
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Affects versions
Created 9 April 2019 at 12:55
Updated 20 May 2020 at 18:17
Across multiple servers, and versions of Lucee, the service will occasionally throw a "The resources may not be accessed if they are not currently started" after a restart or service recycle.
Reviewing the logs, it appears that Lucee cannot access certain tags that are in the server context/library/tag folder. For us, it is normally Dump.cfc. However, depending on the code base it can also be other tags in that folder.
For a stack trace, see this article:
https://dev.lucee.org/t/lucee-server-error-the-resources-may-not-be-accessed-if-they-are-not-currently-started/2268
If you stop the Lucee service, and then start it, the problem will go away.
It is very difficult to replicate the problem because it doesn't happen all of the time. From my observation, it's more likely to happen with a service recycle than a stop/start.