Skip to:

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

Lucee5 new install (or upgrade from lucee4.5) issue on cache region

Description

Hi,
we are trying to upgrade our lucee production environment from 4.5 version to 5.0.

In our projects we use few time cfquery tag with cachedwithin parameter.

After a fresh installation (or a simple upgrade from lucee4.5), when we start server and try to access the site we obtain this error message :
there is no cache with name [QUERY]

Going deeply in the logs, after verify the QUERY cache region from lucee console we get :
lucee.runtime.exp.SecurityException: write access is protected

and
at server_cfm$cf.call(/Users/mic/Projects/Lucee/Lucee5/core/src/main/cfml/context/admin/server.cfm:2)

that seems to be a local path..

See the entire stack trace in the attached file for more information.

What we have to do in order to solve the problem?

Thanks in advance!
Regards,
Sergio Belli

Environment

Ubuntu 14.04.3 LTS server on amazon ec2 machine.

Attachments

1
  • 08 Jun 2016, 09:36 am

Activity

Show:

Pothys - MitrahSoft 6 February 2018 at 06:20

Closed as per reporter's comment.

Sergio Belli 2 February 2018 at 08:43

You can close the ticket.
Thank you.

Pothys - MitrahSoft 2 February 2018 at 08:30

Hi ,

Did you see above comments from . Please confirm the issue is still reproduced or not if not can I close the ticket?

Michael Offner 19 September 2016 at 10:02

log entry is unrelated to this, this shows a try to access the admin without a password.
we need more details about the query issue:

  • how does the failing query look like?

  • any log on this

  • still happening when you update tp most recent version?

Cannot Reproduce

Details

Assignee

Reporter

Priority

Labels

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 8 June 2016 at 09:44
Updated 6 February 2018 at 06:20
Resolved 6 February 2018 at 06:20

Flag notifications