[UTILS-16] CachedObject gets out of sync when multiple CachedObjects share the same cache Created: 26/Sep/13  Updated: 12/Oct/13  Resolved: 12/Oct/13

Status: Resolved
Project: Utils
Component/s: None
Affects Version/s: 0.7
Fix Version/s: 0.8

Type: Bug Priority: Major
Reporter: Erik Brakkee Assignee: Erik Brakkee
Resolution: Fixed Votes: 0
Labels: None
Environment: all

Create two CachedObject instances with the same cache that both represent the same object. Invalidate the first cached object. Now use the second cached object. After that use the first cached object again. Now a null value is returned which is only refreshed after the cache for the entry expires.

Comment by Erik Brakkee [ 12/Oct/13 ]
The cached object now uses the non-null value obtained from the cache instead of the locally cached value in case of a cache hit. The locally cached value is only used when computing the new value fails in case of a cache miss.
Generated at Tue May 18 09:09:11 CEST 2021 using JIRA 6.1#6144-sha1:2e5032834b5e9b089289c97f8425a146c3cf4464.