Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Resources may not be accessed if they are not currently started

Description

The web and web-inf files for our install reside on a clustered resource. Whenever the cluster fails over to a new node, Lucee starts returning the following error for any file upload. It does not stop erroring until we restart the Lucee service. It seems that something internal to Lucee stops running if the drive is temporarily unavailable. During failover, the drive is not available for about 30 seconds.

lucee.runtime.exp.NativeException: The resources may not be accessed if they are not currently started
at lucee.runtime.exp.NativeException.newInstance(NativeException.java:73)
at lucee.runtime.op.Caster.toPageException(Caster.java:3201)
at lucee.runtime.op.Caster.toPageException(Caster.java:3176)
at web_cfm$cf.call(/admin/web.cfm:281)
at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:928)
at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:842)
at lucee.runtime.listener.ModernAppListener._onRequest(ModernAppListener.java:224)
at lucee.runtime.listener.MixedAppListener.onRequest(MixedAppListener.java:43)
at lucee.runtime.PageContextImpl.execute(PageContextImpl.java:2408)
at lucee.runtime.PageContextImpl._execute(PageContextImpl.java:2398)
at lucee.runtime.PageContextImpl.executeCFML(PageContextImpl.java:2366)
at lucee.runtime.engine.Request.run(Request.java:34)

Environment

Windows 2008R2

Activity

Show:

Michael Sprague 6 April 2018 at 15:21

We abandoned all use of clustered network (UNC path) drives for the WEB-INF folder. We modified our config to place the WEB-INF folders on the local drive. I have no easy way to replicate the way it was set up before. Since I am the only one to report the problem, I think you can close this ticket.

Pothys - MitrahSoft 6 April 2018 at 14:16

Hi ,

Did you get any update on this & Can you please check once again on lucee latest version and let me know.

Michael Sprague 18 July 2017 at 00:16
Edited

I believe the resource can be one of two things...

1. A file directory where uploaded files are placed.
2. Cached files stored in the WEB-INF folder.

In both cases, the actual files/directories are available to the OS, but Lucee will not connect to them until Lucee is restarted.

It may be some time before I can test this on a new snapshot, because the clustered drives are on our LIVE web environment and the failover creates down time for our site.

Michael Offner 17 July 2017 at 06:37

can you give more details on what the "resource" is?
Can you please test the same with the latest snapshot version and report again the stacktrace (that will be different).

Cannot Reproduce

Details

Assignee

Reporter

Priority

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 11 July 2017 at 18:44
Updated 7 April 2018 at 07:41
Resolved 7 April 2018 at 07:41