Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-619

CacheManager (Memory Management in Jackrabbit)

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.2.1
    • Component/s: jackrabbit-core
    • Labels:
      None

      Description

      Jackrabbit can run out of memory because the the combined size of the various caches is not managed. The biggest problem (for me) is the combined size of the o.a.j.core.state.MLRUItemStateCache caches. Each session seems to create a few of those caches, and each one is limited to 4 MB by default.

      I have implemented a dynamic (cache-) memory management service that distributes a fixed amount of memory dynamically to all those caches.

      Here is the patch

        Attachments

        1. jackrabbit-cachemanager-config.patch
          5 kB
          Jaka Jaksic
        2. cacheManager7.txt
          2 kB
          Thomas Mueller
        3. stack.txt
          41 kB
          Xiaohua Lu
        4. cacheManager6.txt
          2 kB
          Thomas Mueller
        5. cacheManager5.txt
          41 kB
          Thomas Mueller
        6. cacheManager2.txt
          15 kB
          Thomas Mueller
        7. cacheManager.txt
          15 kB
          Thomas Mueller

          Issue Links

            Activity

              People

              • Assignee:
                stefan@jira Stefan Guggisberg
                Reporter:
                tmueller Thomas Mueller
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: