EHCache connections have been stable until upgrading to EHCache Extension version 22.214.171.124. The prior version we were running was 126.96.36.199, and we never had any problems. After upgrading, we began experiencing a general instability with all EHCache instances defined on the server. We have not determined the cause of the problem, but rolling back to 188.8.131.52 seems to have removed the issue.
The symptoms are:
1. Verifying cache connections in the server/web admin results in a: "Error java.lang.NullPointerException"
2. Calling cachePut() throws the same error.
3. Verifying an EHCache connection immediately after creating a new one generates the same error.
Symptoms do not go away unless you restart Lucee FROM WITHIN THE SERVER ADMIN. Restarting the Lucee Service on Windows does not clean the EHCache state. This was confusing because I always thought that restarting Lucee from the Services snap in does restart Lucee, but apparently that is not entirely true.
Windows 7 x64
NOTE: This issue does occur on Lucee v.184.108.40.206, but also occurs on the lower version of v.220.127.116.11, which is what I have installed, but I cannot enter this in the "Affects Version/s" pull down above because this version is not listed.
it only happens when a cache is defined in server admin
as workaround define caches only in web admin
This fix is only available as SNAPSHOT yet, mean you cannot install in Lucee 5.2 Admin (only in 5.3).
This means you have do download the fix here:
and copy to "/lucee-server/deploy".
A release will follow on a later time
Lucee version 18.104.22.168-SNAPSHOT bundles that Extension, means when you update to 22.214.171.124-SNAPSHOT you will have that version.
Now I can't get any ehcache's to work using Lucee 126.96.36.199 and EHCache 188.8.131.52, which I thought were the stable versions. I wonder if I somehow corrupted my cache settings. How might I reset them? My C:\lucee\tomcat\lucee-server\context\ehcache folder is empty.