Uploaded image for project: 'Lucee Development'
  1. LDEV-1332

The CacheManager has been shut down. It can no longer be used.

    Details

    • Sprint:
      May-June 2017 Sprint, July 2017 Sprint, August 2017 Sprint

      Description

      After updating to v5.2.1.9 (why is there no '5.2.1.9 in the 'Affects Versions' dropdown, btw?) I got the following error on one of my VivioTech VPS Lucee instances:

      Action: home:main.default
      Error: The CacheManager has been shut down. It can no longer be used.
      Type: java.lang.IllegalStateException
      Details: 
      

      When I went to the web admin and tried to verify the cache connection it simply returned 'ERROR'. I ended up deleting and recreating the cache and the site came back up.

      I will add further notes if this behavior returns (e.g. after some period of inactivity on the site, which is what I suspect the underlying issue to be).

      I originally downgraded the server and set the update to manual, but somehow the server keeps getting updated to 5.2.1.9 despite having set that (perhaps VivioTech has a script that updates them, perhaps your 'manual' selection is borked - not sure which yet, will report another bug if I determine it's Lucee and not VivioTech), so now I'm trying to figure out how and why I'm getting this error instead of just rolling it back. Have the latest ehcache extension installed (2.10.0.21).

      Using code from: https://github.com/ddspringle/framework-one-secure-auth
      Demo server at: https://sa.vsgcom.net/ (the instance having this issue)

        Attachments

          Activity

            People

            • Assignee:
              michaeloffner Michael Offner
              Reporter:
              ddspringle Denard Springle
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: