Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-3007

Implement caching in the RiceApplicationConfigurationMediationServiceImpl

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0
    • Component/s: Development
    • Labels:
      None
    • Similar issues:
      KULRICE-2315Implement caching of data to the IdentityManagementService implementation
      KULRICE-3006Implement Parameter caching in the ParameterProxyService
      KULRICE-8327Implement caching for Message Service
      KULRICE-2452Implement cluster-aware caching on KNS System Parameters
      KULRICE-5319Implement caching on remote soap services
      KULRICE-2385Implement caching on the IdentityManagementService - Phase 2
      KULRICE-7258Implement caching on ExtensionRepositoryService
      KULRICE-2384Implement caching on the IdentityManagementService - Phase 1
      KULRICE-2418Implement cache aging and flushing on PersonServiceImpl
      KULRICE-1208Implement caching in ActionFormUtilMap
    • Rice Module:
      KNS

      Description

      There are two methods on this service, one that can be used to resolve config params, another one that can be used to get non-database components for the parameter service.

      We will want to implement caching on both of these. This will be especially important for the configuration parameters, especially when considering the document search case where variables need to be resolved for every row returned from the search (a lot of the resulting rows could contain the same variables in their doc handler url).

      I think for both of these cases, we don't need a cluser-aware cache but rather a cache with a reasonable timeout (similar to what's in the IdentityManagementService)

        Issue Links

          Activity

          Hide
          Jeremy Hanson added a comment -

          I have this done locally, and currently have the timeout set to 60 minutes. Is this too much? What should this be set to?

          Show
          Jeremy Hanson added a comment - I have this done locally, and currently have the timeout set to 60 minutes. Is this too much? What should this be set to?
          Hide
          Jeremy Hanson added a comment -

          Caching has been implemented.

          Show
          Jeremy Hanson added a comment - Caching has been implemented.
          Hide
          Eric Westfall added a comment -

          Bulk change of all Rice 1.0 issues to closed after public release.

          Show
          Eric Westfall added a comment - Bulk change of all Rice 1.0 issues to closed after public release.

            People

            • Assignee:
              Jeremy Hanson
              Reporter:
              Eric Westfall
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 day
                1d
                Remaining:
                Remaining Estimate - 1 day
                1d
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel