[jboss-cvs] JBoss Messaging SVN: r7882 - branches/JBMESSAGING-1742/docs/userguide/en/modules.

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

Author: gaohoward
Date: 2009-10-29 04:40:02 -0400 (Thu, 29 Oct 2009)
New Revision: 7882

Modified:
   branches/JBMESSAGING-1742/docs/userguide/en/modules/configuration.xml
Log:
doc


Modified: branches/JBMESSAGING-1742/docs/userguide/en/modules/configuration.xml
===================================================================
--- branches/JBMESSAGING-1742/docs/userguide/en/modules/configuration.xml	2009-10-29 03:15:36 UTC (rev 7881)
+++ branches/JBMESSAGING-1742/docs/userguide/en/modules/configuration.xml	2009-10-29 08:40:02 UTC (rev 7882)
@@ -1663,6 +1663,22 @@
           <para>The number of consumers currently consuming from the
           queue.</para>
         </section>
+
+        <section id="conf.destination.queue.attributes.dropoldmessageonredeploy">
+          <title>DropOldMessageOnRedeploy</title>
+
+          <para>When you re-deploy a queue service with a clustered attribute different from the one with which it has been 
+          previously deployed, all remaining messages in the queue will be deleted after the re-deployment if you set this
+          parameter to true. Otherwise the messages will be reserved. Default is false.
+          <warning>
+               When you re-deploy a destination, you need to shut
+               down all the nodes in the cluster, make proper configuration change and then restart the nodes. 
+               Redeploying from a non-clustered queue to a clustered one requires you set the Clustered attribute to true, and
+               add the queue service configuration to each node. Redeploying from a clustered queue to a non-clustered requires 
+               you set the Clustered attribute to false in one of the queue configurations and delete all others in the cluster.
+          </warning>
+          </para>
+        </section>
       </section>
 
       <section id="conf.destination.queue.operations">
@@ -1948,6 +1964,22 @@
           <para>The count of all non durable subscriptions on this
           topic</para>
         </section>
+
+        <section id="conf.destination.topic.attributes.dropoldmessageonredeploy">
+          <title>DropOldMessageOnRedeploy</title>
+
+          <para>When you re-deploy a topic service with a clustered attribute different from the one with which it has been 
+          previously deployed, all remaining messages of its durable subscribers will be deleted after the re-deployment if you set this
+          parameter to true. Otherwise the messages will be reserved. Default is false.
+          <warning>
+               When you re-deploy a destination, you need to shut
+               down all the nodes in the cluster, make proper configuration change and then restart the nodes. 
+               Redeploying from a non-clustered topic to a clustered one requires you set the Clustered attribute to true, and
+               add the topic service configuration to each node. Redeploying from a clustered topic to a non-clustered one requires 
+               you set the Clustered attribute to false in one of the topic configurations and delete all others in the cluster.
+          </warning>
+          </para>
+        </section>
       </section>
 
       <section id="conf.destination.topic.operations">