Mailing-List: contact commits-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: commits@jackrabbit.apache.org
Date: Wed, 19 Dec 2007 11:08:42 -0000
Message-ID: <20071219110842.19286.61750@eos.apache.org>
Subject: [Jackrabbit Wiki] Update of "CacheManager" by ThomasMueller

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The following page has been changed by ThomasMueller:
http://wiki.apache.org/jackrabbit/CacheManager

------------------------------------------------------------------------------
  The CacheManager manages the size of the caches used in Jackrabbit (MLRUItem``State``Cache objects). The combined size of all caches must be limited to avoid out of memory problems. Without CacheManager, Jackrabbit can run out of memory because the the combined size of the various caches is not managed. This mechanism is not the definitive solution; it may be desirable to internally use only one cache.
  
- The CacheManager does not control the memory used by unsaved data (data in the transient space).
+ The CacheManager does not control the memory used by unsaved data (data in the transient space). If you get out of memory exceptions, check that your application calls Node.save() or (even better) Session.save() from time to time. Unsaved changes are kept in memory with the current Jackrabbit.
  
  The maximum size for all caches in CacheManager is 16 megabytes by default, but it can be changed like this: