[KULRICE-5942] See if we can improve our cache flushing with new Spring cache annotations Created: 09/Nov/11  Updated: 23/Feb/12  Resolved: 10/Jan/12

Status: Closed
Project: Kuali Rice Development
Component/s: Version Compatibility
Affects Version/s: 2.0.0-b1
Fix Version/s: 2.0.0-rc1, 2.0
Security Level: Public (Public: Anyone can view)

Type: Task Priority: Critical
Reporter: Jeremy Hanson Assignee: Jeremy Hanson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Similar issues:
KULRICE-5357update our caching solution for rice.
KULRICE-2418Implement cache aging and flushing on PersonServiceImpl
KULRICE-7258Implement caching on ExtensionRepositoryService
KULRICE-3222Ensure that ParameterServerService can be remoted and improve caching in ParameterServiceProxyImpl
KULRICE-5808Fix cache errors when injecting service containing cache annotations with spring
KULRICE-5097KIM Caches are not being flushed as required.
KULRICE-5967Investigate whether we should publish methods on services to flush caches
KULRICE-12457KRMS error and cache flush messages not appearing right
KULRICE-8955MessageServiceImpl getDefaultLocaleCode Caching
KULRICE-12363Make priority of KIM cache messages configurable
KAI Review Status: Not Required
KTI Review Status: Not Required


Spring 3.1RC2 allows us to use a finer grained cache flushing. Seems like it could be useful for performance tuning.


We should investigate using this and make appropriate changes

Comment by Jeremy Hanson [ 10/Jan/12 ]

The answer is that we can improve on things a bit with this, in most cases our caches/cache keys are too complex to do a lot of this stuff, and with the nesting of objects (doc types, routing rules, membership stuff), our only real answer is to do full cache flushes in many instances.

That said, some work was done to clean things up a bit.

Comment by Jessica Coltrin (Inactive) [ 23/Feb/12 ]

Closing since these items are now in the release notes.

Generated at Tue Jun 02 21:44:09 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.