Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-33381

Unused cache properties for calendar

    Details

    • Type: Bug
    • Status: Verified
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 19.0
    • Fix Version/s: 12.0, 19.0
    • Component/s: Calendar
    • Labels:
    • 12 status:
      Resolved
    • Property addition/change required:
      Yes
    • Test Plan:
      Hide

      1. Go to the Calendar tool, then Merge External Calendars.
      2. Suscribe to an external calendar, for example, you can use an ICAL url from a Google calendar.
      3. Check that the events of external calendar has been incorporated to Sakai calendar tool.
      4. Create a new event in Google calendar.
      5. Check that the new event firstly isn't in Sakai calendar tool.
      6. Wait the cache refresh time (default: 120 minutes).
      7. Check that the new event is now in Sakai calendar tool.

      Show
      1. Go to the Calendar tool, then Merge External Calendars. 2. Suscribe to an external calendar, for example, you can use an ICAL url from a Google calendar. 3. Check that the events of external calendar has been incorporated to Sakai calendar tool. 4. Create a new event in Google calendar. 5. Check that the new event firstly isn't in Sakai calendar tool. 6. Wait the cache refresh time (default: 120 minutes). 7. Check that the new event is now in Sakai calendar tool.

      Description

      The cache properties for the calendar tool defined in sakai.properties file are:

      # 4. Subscription cache settings (optional)
      # Institutional subscription defaults: reload every 120min
      # User subscriptions defaults: max 32 subscriptions in memory, reload every 120min
      # calendar.external.subscriptions.institutional.cachetime=120
      # calendar.external.subscriptions.user.cacheentries=32
      # calendar.external.subscriptions.user.cachetime=120
      

      After some research, we've noticed that they have never been read/used, the cache time has always the value of 12 hours and the max entries is 1000.

      We've had some problems with it recently and we believe that the cache properties should be used instead of the hardcoded values.
      Besides, we should create a new property calendar.external.subscriptions.institutional.cacheentries.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  juanarcadio Juan Arcadio Martinez Carceles
                  Reporter:
                  juanarcadio Juan Arcadio Martinez Carceles
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code