-
Bug
-
Resolution: Done
-
Major
-
6.0.0.Final
Currently the CacheLoaderInterceptor does the following check to determine if it should check the loader for a value
if (e == null || e.isNull() || e.getValue() == null) {
Unfortunately this means it checks the loader when a null value is in the entry when using RR. This can cause an issue if another transaction commits that key and puts a value that results in that value being inserted into the loader.
This also is a performance issue for RR, since it has to check the loader over and over for a given key even if it was found null the first time.
Initial thought is to do something like setSkipRemoteGet and that could actually be used for a dual purpose possibly.
- is related to
-
ISPN-3797 DataContainer should interact atomically with Persistence
- Closed