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

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:

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)

Environment

VivioTech Linux VPS

Activity

Show:
adiedler
May 29, 2017, 4:18 PM

Do you face the issue again since reboot and watching with FR?

adiedler
May 29, 2017, 8:41 PM

I got the full stack trace:

Denard Springle
May 30, 2017, 3:27 PM

I have not seen this issue again since the server reboot.

Michael Offner
June 12, 2017, 2:09 PM

also check out

Michael Offner
July 31, 2017, 10:06 AM

FYI: the auto update functionality is untouched for years and in case of an issue it will NOT run automatically, it will do nothing.
So it is extremely unlikely Lucee itself updates auto if that setting is not set to auto-

Fixed

Assignee

Michael Offner

Reporter

Denard Springle

Priority

Critical

Labels

Fix versions

Sprint

None

Affects versions

Configure