Fixed
Details
Assignee
Michael OffnerMichael OffnerReporter
JPJPPriority
NewLabels
Fix versions
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
Sprint
NoneAffects versions
Details
Details
Assignee
Michael Offner
Michael OffnerReporter
JP
JPPriority
Labels
Fix versions
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
Sprint
None
Affects versions
Created 6 November 2017 at 22:38
Updated 11 February 2021 at 16:46
Resolved 22 December 2017 at 14:32
EHCache connections have been stable until upgrading to EHCache Extension version 2.10.0.25. The prior version we were running was 2.10.0.22, 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 2.10.0.22 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.