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

CacheManager (Memory Management in Jackrabbit)

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.2.1
    • jackrabbit-core
    • 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. cacheManager.txt
          15 kB
          Thomas Mueller
        2. cacheManager2.txt
          15 kB
          Thomas Mueller
        3. cacheManager5.txt
          41 kB
          Thomas Mueller
        4. cacheManager6.txt
          2 kB
          Thomas Mueller
        5. cacheManager7.txt
          2 kB
          Thomas Mueller
        6. jackrabbit-cachemanager-config.patch
          5 kB
          Jaka Jaksic
        7. stack.txt
          41 kB
          Xiaohua Lu

        Issue Links

          incorporates

          Bug - A problem which impairs or prevents the functions of the product. JCR-625 Memory is not freed up when jackrabbit-server war is redeployed in tomcat

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              stefan@jira Stefan Guggisberg
              thomasm Thomas Mueller
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: