[KULRICE-12363] Make priority of KIM cache messages configurable Created: 02/Apr/14  Updated: 15/May/14  Resolved: 03/Apr/14

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: None
Fix Version/s: 2.5
Security Level: Public (Public: Anyone can view)

Type: Improvement Priority: Major
Reporter: James Bennett Assignee: Unassigned
Resolution: Complete Votes: 0
Labels: IU_Enhancement_Contribution
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Similar issues:
KULRICE-2727Make KIM caching options configurable through config properties
KULRICE-7533KualiPropertyMessageResources does not cache messages
KULRICE-3960make "Logged in User" message configurable
KULRICE-2418Implement cache aging and flushing on PersonServiceImpl
KULRICE-2721Add switch on KIM Configurer to make run in local or remote modes
KULRICE-14090Make improvements to KIM integration performance
KULRICE-12485Adding/Removing a role doesn't take effect even if you clear the kim cache
KULRICE-8298Add ehCache caching setup to KRAD
KULRICE-6436Tune ehcache configuration for the various rice modules
KULRICE-6482Document cache configuration and overriding
Rice Module:
KIM
KAI Review Status: Not Required
KTI Review Status: Not Required
Code Review Status: Not Required
Contributing Institution: Indiana Univ
Include in Release Notes?:
Yes

 Description   

At IU we had a lot of issues with KC after moving to Rice 2. They update roles in KIM when people initiate certain documents which would trigger a flush of several caches in KIM. This lead to a cache flush message going out to every system very regularly. That caused an abundance of cache flush messages (tens of thousands) to build up in our message queue which would prevent documents from routing since the KIM messages had a higher priority. We ultimately decided to decrease the priority of KIM cache messages so they were lower than document routing which helped prevent this problem from happening again. We would like the priority of KIM messages to be configurable and have a default of 3 like is currently used. Then we can override the configuration property at IU to set the priority level we use here.



 Comments   
Comment by Shravya Saripella (Inactive) [ 03/Apr/14 ]

Contribution complete

Comment by Jessica Coltrin (Inactive) [ 15/May/14 ]

moving IU contributions to 2.5

Generated at Thu Apr 02 00:57:59 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.