Uploaded image for project: 'Advanced Cache'
  1. Advanced Cache
  2. MGNLADVCACHE-25

The ServeUntilRecachedPolicy and EagerRecachePolicy use a single global timestamp for all caches.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Neutral Neutral
    • 1.6
    • 1.4, 1.5
    • None

      Both the ServeUntilRecachedPolicy and EagerRecachePolicy use a timestamp to determine if objects should be refreshed. However the flushpolicies
      (EagerRecacheFlushPolicy and NotifyFlushListeningPolicy) they use store the timestamp in the config workspace under the advanced-cache module.

      There is only one timestamp there, so the timestamp is global for all caches configured with that policy so this does not work in multisite configurations or on single site with multiple cache configurations.

        Acceptance criteria

              rkovarik Roman Kovařík
              rico.jansen Rico Jansen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD