external-software/github_OpenIdentityPlatform_OpenDJ.git

			@@ -23,7 +23,7 @@
			! CDDL HEADER END
			!
			!
			! Portions Copyright 2007 Sun Microsystems, Inc.
			! Portions Copyright 2007-2008 Sun Microsystems, Inc.
			! -->
			<adm:managed-object name="file-system-entry-cache"
			plural-name="file-system-entry-caches"
			@@ -37,17 +37,17 @@
			track of the entries.
			</adm:synopsis>
			<adm:description>
			For the best performance the JE database should reside in a memory
			based file system, although any file system will do for this cache
			to function. Entries are maintained either by FIFO (default) or LRU
			(configurable) based list implementation. Cache sizing is based on
			For best performance, the JE database should reside in a memory
			based file system although any file system will do for this cache
			to function. Entries are maintained either by FIFO (default) or LRU-based
			(configurable) list implementation. Cache sizing is based on
			the size of free space available in the file system, such that if
			enough memory is free, then adding an entry to the cache will not
			require purging, but if more than a specified size of the file
			require purging. If more than the specified size of the file
			system available space is already consumed, then one or more entries
			will need to be removed in order to make room for a new entry. It is
			need to be removed in order to make room for a new entry. It is
			also possible to configure a maximum number of entries for the cache.
			If this is specified, then the number of entries will not be allowed
			If this is specified, then the number of entries are not allowed
			to exceed this value, but it may not be possible to hold this many
			entries if the available memory fills up first. Other configurable
			parameters for this cache include the maximum length of time to block
			@@ -55,7 +55,7 @@
			used to define criteria for determining which entries are stored in
			the cache. If a set of filters are provided then an entry must match
			at least one of them in order to be stored in the cache.
			JE environment cache size can also be configured either as percentage
			JE environment cache size can also be configured either as a percentage
			of the free memory available in the JVM, or as an absolute size in
			bytes. This cache has a persistence property which, if enabled,
			allows for the contents of the cache to persist across server or
			@@ -204,7 +204,7 @@
			<adm:requires-admin-action>
			<adm:none>
			<adm:synopsis>
			Changing this property will only affect the encoding of the
			Changing this property only affects the encoding of the
			cache entries put in the cache after the change is made. It
			will not be retroactively applied to existing cache entries.
			</adm:synopsis>
			@@ -226,7 +226,7 @@
			</adm:property>
			<adm:property name="db-cache-percent">
			<adm:synopsis>
			The maximum memory usage for the internal JE cache as a percentage
			Specifies the maximum memory usage for the internal JE cache as a percentage
			of the total JVM memory.
			</adm:synopsis>
			<adm:default-behavior>
			@@ -245,7 +245,7 @@
			</adm:property>
			<adm:property name="db-cache-size">
			<adm:synopsis>
			The maximum JVM memory usage in bytes for the internal JE cache.
			Specifies the maximum JVM memory usage in bytes for the internal JE cache.
			</adm:synopsis>
			<adm:default-behavior>
			<adm:defined>
			@@ -269,11 +269,11 @@
			</adm:synopsis>
			<adm:description>
			Any Berkeley DB Java Edition property can be specified using the
			following form: property-name=property-value Refer to OpenDS
			following form: property-name=property-value. Refer to the OpenDS
			documentation for further information on related properties, their
			implications and range values. The definitive identification of
			all the property parameters available in the example.properties
			file of Berkeley DB Java Edition distribution.
			file in the Berkeley DB Java Edition distribution.
			</adm:description>
			<adm:default-behavior>
			<adm:defined>