Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-1692

Slow memory leak in StatefulTreeCache if removal timeout is not configured.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.1.5
    • 1.0.0-CR1
    • cache, Clustering
    • None

      StatefulTreeCache maintains a Map<GUID, Long> of all beans that is used 1) to drive removal of expired beans, and 2) to provide the answer to the Cache.getTotalSize() management method. Problem is entries will never be removed from this map if @CacheConfig.removalTimeoutSeconds is left at the default value of 0.

      Solution is to not use the Map if removalTimeoutSeconds is 0. Implement a different mechanism to answer Cache.getTotalSize().

              bstansbe@redhat.com Brian Stansberry
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: