[jboss-cvs] JBoss Messaging SVN: r3150 - trunk/docs/userguide/en/modules.

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

Author: clebert.suconic at jboss.com
Date: 2007-09-27 18:45:39 -0400 (Thu, 27 Sep 2007)
New Revision: 3150

Modified:
   trunk/docs/userguide/en/modules/configuration.xml
Log:
http://jira.jboss.com/jira/browse/JBMESSAGING-1078 - docs

Modified: trunk/docs/userguide/en/modules/configuration.xml
===================================================================
--- trunk/docs/userguide/en/modules/configuration.xml	2007-09-27 20:29:57 UTC (rev 3149)
+++ trunk/docs/userguide/en/modules/configuration.xml	2007-09-27 22:45:39 UTC (rev 3150)
@@ -2259,7 +2259,9 @@
 
       <attribute name="SlowConsumers">false</attribute>
       
-      <attribute name="DefaultTempQueueFullSize">50000</attribute> 
+      <attribute name="StrictTck">true</attribute>
+
+      <attribute name="DefaultTempQueueFullSize">50000</attribute>
       
       <attribute name="DefaultTempQueuePageSize">1000</attribute> 
             
@@ -2317,16 +2319,25 @@
 	           </para>
 	        </section>
 
-               <section id="conf.connectionfactory.attributes.slowconsumers">
+              <section id="conf.connectionfactory.attributes.slowconsumers">
 	           <title>SlowConsumers</title>
 	
 	           <para>
 	            If you have very slow consumers, then you probably want to make sure they don't buffer any messages.
                     Since this can prevent them from being consumed by faster consumers.
 	           </para>
-	        </section>		      
+	        </section>
 
-	        <section id="conf.connectionfactory.attributes.tempqueuepaging">
+           <section id="conf.connectionfactory.attributes.tckstrictbehavior">
+              <title>StrictTck</title>
+              <para>
+                 As part of JMS specification foreign messages should receive a new destination when the message is sent, but when the Bridge is playing with other providers
+                 such as ActiveMQ this could affect the regular operation on those providers. We disabled that by default but if you need this behavior activated you should just set this attribute to
+                 True on the ConnectionFactory.
+              </para>
+           </section>
+
+                <section id="conf.connectionfactory.attributes.tempqueuepaging">
 	           <title>Temporary queue paging parameters</title>
 	
 	              <para>DefaultTempQueueFullSize, DefaultTempQueuePageSize, DefaultTempQueueDownCacheSize are optional attributes that determine the default paging parameters to be used for