No, it just isn't used very heavily. It probably doesn't need to even exist but it certainly is used on occasion. Closing as won't fix though the limits could be tuned or it could be removed if someone wanted to.

(One random instance I looked at)
org.sakaiproject.event.api.NotificationService.cache: count:16 hits:3 misses:3 hit%:50

[ name = org.sakaiproject.event.api.NotificationService.cache status = STATUS_ALIVE eternal = false overflowToDisk = false maxElementsInMemory = 10000 maxElementsOnDisk = 0 memoryStoreEvictionPolicy = LRU timeToLiveSeconds = 300 timeToIdleSeconds = 300 diskPersistent = false diskExpiryThreadIntervalSeconds = 120 cacheEventListeners: net.sf.ehcache.statistics.LiveCacheStatisticsWrapper hitCount = 3 memoryStoreHitCount = 3 diskStoreHitCount = 0 missCountNotFound = 3 missCountExpired = 0 ]

I am unassigning this issue as it gives the wrong impression. I dont have enough hours in the day to look at this issue at the moment and keeping it assigned to me give the reporter hope that I might be able to look at it. I am very sorry. If this issue is a real blocker for production then I would suggest you look for resource in the community to fix the problem, I am happy to respond to emails and guide. Where the code base is Rwiki or Search, I have absolutely no problem with someone else working on the code, this after all is a community.