jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-937) CacheManager max memory size
Date Tue, 18 Sep 2007 07:51:43 GMT

     [ https://issues.apache.org/jira/browse/JCR-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Mueller resolved JCR-937.
--------------------------------

    Resolution: Cannot Reproduce
      Assignee: Thomas Mueller

If the problem is really too many open sessions maybe we should add a limit on the number
of sessions, or warn if the application did not close sessions?

I am resolving this problem until it can be reproduced. Please re-open if necessary.

> CacheManager max memory size
> ----------------------------
>
>                 Key: JCR-937
>                 URL: https://issues.apache.org/jira/browse/JCR-937
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.3
>            Reporter: Xiaohua Lu
>            Assignee: Thomas Mueller
>            Priority: Minor
>
> I have ran into OutOfMemory a couple of times with Jackrabbit (cluster, 4 nodes, each
has 1G mem heap size). 
> After adding some debug into the CacheManager, I noticed that maxMemorySize (default
to 16M) is not really honored during resizeAll check.  Each individual MLRUItemStateCache
seems to honor the size, but the total number/size of MLRUItemStateCache is not. If you put
some print statement of totalMemoryUsed and unusedMemory, you can see that totalMemoryUsed
is more than 16M and unusedMemory is negative. 
> The other problem we have noticed during the profiling is there are a lots of other in
memory objects that are consuming memory but not included in CacheManager caches control.
One example is CachingHierarchyManager which consumed 58M out of 242M through its use of PathMap.
If CacheManager's maxSize can control the total cache size used by Jackrabbit, that would
be easier from a management's perspective. (btw, upper_limit in CachingHierarchyManager is
hardcoded and can't be control from outside)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message