[jboss-cvs] JBoss Messaging SVN: r8011 - projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_8/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: laubai
Date: 2010-04-22 20:08:52 -0400 (Thu, 22 Apr 2010)
New Revision: 8011

Modified:
   projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_8/en-US/configuration.xml
Log:
Added warning about large destination paging parameters.

Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_8/en-US/configuration.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_8/en-US/configuration.xml	2010-04-22 11:47:53 UTC (rev 8010)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_8/en-US/configuration.xml	2010-04-23 00:08:52 UTC (rev 8011)
@@ -1618,29 +1618,34 @@
           messages held by the queue or topic subscriptions in memory at any
           one time. The actual queue or subscription can hold many more
           messages than this but these are paged to and from storage as
-          necessary as messages are added or consumed.</para>
+          necessary as messages are added or consumed. If no value is 
+          specified, the default is <literal>75000</literal>.</para>
 
           <para><literal>PageSize</literal> - When loading messages from the
           queue or subscription this is the maximum number of messages to
-          pre-load in one operation.</para>
+          pre-load in one operation. If no value is specified, the default is
+          <literal>2000</literal>.</para>
 
           <para><literal>DownCacheSize</literal> - When paging messages to
           storage from the queue they first go into a "Down Cache" before
           being written to storage. This enables the write to occur as a
           single operation thus aiding performance. This setting determines
           the max number of messages that the Down Cache will hold before they
-          are flushed to storage.</para>
+          are flushed to storage. If no value is specified, the default is
+          <literal>2000</literal>.</para>
 
-          <para>If no values for <literal>FullSize</literal>,
-          <literal>PageSize</literal>, or <literal>DownCacheSize</literal> are
-          specified they will default to values 75000, 2000, 2000
-          respectively.</para>
-
           <para>If you want to specify the paging parameters used for
           temporary queues then you need to specify them on the appropriate
           connection factory. See connection factory configuration for
           details.</para>
 
+          <warning>
+            <title>Large values in destination paging parameters</title>
+            <para>
+              Configuring large values in destination paging parameters can cause <exceptionname>OutOfMemory</exceptionname> exceptions when used with JDBC driver version 11.2.0.1.0 and Oracle 11g R1, R2 and RAC. For more information, see the Known Issues section in the JBoss Enterprise Application Platform 5.0.1 Release Notes.
+            </para>
+          </warning>
+
   <formalpara>
           <title>CreatedProgrammatically</title>