Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major 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

      1. stack.txt
        41 kB
        Xiaohua Lu
      2. jackrabbit-cachemanager-config.patch
        5 kB
        Jaka Jaksic
      3. cacheManager7.txt
        2 kB
        Thomas Mueller
      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 Guggisberg
              Reporter:
              Thomas Mueller
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development