[jboss-cvs] JBossCache/docs/faq/en ...
Manik Surtani
msurtani at jboss.com
Mon Oct 23 13:39:00 EDT 2006
User: msurtani
Date: 06/10/23 13:39:00
Modified: docs/faq/en master.xml
Log:
JBCACHE-684
Revision Changes Path
1.39 +10 -5 JBossCache/docs/faq/en/master.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: master.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/docs/faq/en/master.xml,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -b -r1.38 -r1.39
--- master.xml 16 Oct 2006 09:19:51 -0000 1.38
+++ master.xml 23 Oct 2006 17:39:00 -0000 1.39
@@ -1191,6 +1191,13 @@
<tgroup cols="2">
<tbody>
<row>
+ <entry>eventQueueSize</entry>
+
+ <entry>A fine-tuning parameter where you can configure the size of the eviction notification event queue. Defaults to 200,000.
+ </entry>
+ </row>
+
+ <row>
<entry>wakeUpIntervalInSeconds</entry>
<entry>Interval where the clean up thread wakes to process
@@ -1241,9 +1248,8 @@
speed of eviction policy handling timer. Eviction policy handler
will wake up every
<literal>wakeUpIntervalInSeconds</literal>
- seconds to process the eviction event queue. And the queue size is
- fixed at 20000 now. So when the queue size is full, it will create a
- backlog and cause OOM to happen unless the eviction timer catches
+ seconds to process the eviction event queue. So when the queue size is full, it will create a
+ backlog and cause out-of-memory exceptions to happen unless the eviction timer catches
up. To address this problem, in addition to increase the VM heap
size, you can also reduce the
<literal>wakeUpIntervaleInSeconds</literal>
@@ -1251,8 +1257,7 @@
processes the queue more frequently.
</para>
- <para>We will also externalize the queue size so it will be
- configurable in the next release.
+ <para>As of JBoss Cache 2.0.0, the eviction queue size is configurable.
</para>
</answer>
</qandaentry>
More information about the jboss-cvs-commits
mailing list