EHCache java.lang.NullPointerException

Description

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.

Environment

Windows 7 x64
NOTE: This issue does occur on Lucee v.5.2.4.37, but also occurs on the lower version of v.5.2.3.35, 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.

Attachments

1
  • 08 Nov 2017, 12:30 pm

Activity

Show:

JP 11 November 2017 at 05:02

Now I can't get any ehcache's to work using Lucee 5.2.3.35 and EHCache 2.10.0.22, 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.

Michael Offner 10 November 2017 at 21:53

Lucee version 5.2.6.17-SNAPSHOT bundles that Extension, means when you update to 5.2.6.17-SNAPSHOT you will have that version.

Michael Offner 10 November 2017 at 21:20

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:
http://download.lucee.org/?type=extsnap
and copy to "/lucee-server/deploy".

A release will follow on a later time

Michael Offner 10 November 2017 at 15:00

as workaround define caches only in web admin

Michael Offner 10 November 2017 at 15:00

it only happens when a cache is defined in server admin

Fixed

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

Sprint

Affects versions

Created 6 November 2017 at 22:38
Updated 11 February 2021 at 16:46
Resolved 22 December 2017 at 14:32

Flag notifications