Resolution: Won't Fix
Affects Version/s: 11.0
Fix Version/s: None
Previous Issue Keys:KNL-1236
How are you doing prefix based cache invalidation based on events in the new EhCacheMemoryService?
The old BasicMemoryService would register with the EventTrackingService and when modification events appeared that matched the prefix registered for the service would evict any matching cache entries automatically. You can see the old cache implementation getting registered with the EventTrackingService here:
org.sakaiproject.memory.impl.MemCache#MemCache(org.sakaiproject.memory.impl.BasicMemoryService, org.sakaiproject.event.api.EventTrackingService, java.lang.String, net.sf.ehcache.Ehcache)
and the processing of the events here:
I believe this is why the SiteAliasCleanupNotificationActionTest wasn't working as the cache invalidation wasn't happening and so that was why 2 aliases were returned (from the cache) when there should have been none.
[Creating a new issue as KNL-1162 has been marked as verified]