I noticed the documentation for AggrEvents.org.hibernate.cache.spi.UpdateTimestampsCache in ehcache
indicates not replicated but the configuration does replicate values
replicates the value of puts, but does cache invalidation on updates rather than replicating values. Is that logical?
Current doc and configuration:
Documentation needs updating
I think replicateUpdates should be set to true
I don't know why AggrEvents.org.hibernate.cache.spi.UpdateTimestampsCache needs to replicate values to other nodes. It is almost the only thing that does. Also Event Aggregation only runs on one server so seems odd (though I suppose it can switch to another server). uPortal does not do frequent updates to this cache entry so I'd be fine with setting replicateUpdates=true to follow original intent and not be concerned about performance issues.
I don't know why org.hibernate.cache.spi.UpdateTimestampsCache doesn't need to replicate values since AggrEvents does. Thinking it's probably OK but not sure of author's original thinking and intent. It would have been nice if the thinking for why AggrEvent version of entry needs values replicated was documented.