[jboss-cvs] JBoss Messaging SVN: r6912 - trunk/docs/user-manual/en.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed May 20 05:59:56 EDT 2009
Author: ataylor
Date: 2009-05-20 05:59:56 -0400 (Wed, 20 May 2009)
New Revision: 6912
Modified:
trunk/docs/user-manual/en/clusters.xml
Log:
reformatted code and tables for cluster doc
Modified: trunk/docs/user-manual/en/clusters.xml
===================================================================
--- trunk/docs/user-manual/en/clusters.xml 2009-05-20 09:49:23 UTC (rev 6911)
+++ trunk/docs/user-manual/en/clusters.xml 2009-05-20 09:59:56 UTC (rev 6912)
@@ -69,7 +69,8 @@
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<broadcast-period>1000</broadcast-period>
- <connector-ref connector-name="netty-connector" backup-connector-name="backup-connector"/>
+ <connector-ref connector-name="netty-connector"
+ backup-connector-name="backup-connector"/>
</broadcast-group>
</broadcast-groups></programlisting>
<para>Some of the broadcast group parameters are optional and you'll normally use the
@@ -218,7 +219,8 @@
final int groupPort = 9876;
-ConnectionFactory jmsConnectionFactory = new JBossConnectionFactory(groupAddress, groupPort);
+ConnectionFactory jmsConnectionFactory =
+ new JBossConnectionFactory(groupAddress, groupPort);
Connection jmsConnection1 = jmsConnectionFactory.createConnection();
@@ -428,7 +430,9 @@
<entries>
<entry name="ConnectionFactory"/>
</entries>
- <connection-load-balancing-policy-class-name>org.jboss.messaging.core.client.impl.RandomConnectionLoadBalancingPolicy</connection-load-balancing-policy-class-name>
+ <connection-load-balancing-policy-class-name>
+ org.jboss.messaging.core.client.impl.RandomConnectionLoadBalancingPolicy
+ </connection-load-balancing-policy-class-name>
</connection-factory>
</programlisting>
The above example would deploy a JMS connection factory that uses the random connection
@@ -477,9 +481,12 @@
specify the list of servers in the server side configuration file <literal
>jbm-jms.xml</literal>. Let's take a look at an example:</para>
<programlisting><connection-factory name="ConnectionFactory">
- <connector-ref connector-name="my-connector1" backup-connector-name="my-backup-connector1"/>
- <connector-ref connector-name="my-connector2" backup-connector-name="my-backup-connector2"/>
- <connector-ref connector-name="my-connector3" backup-connector-name="my-backup-connector3"/>
+ <connector-ref connector-name="my-connector1"
+ backup-connector-name="my-backup-connector1"/>
+ <connector-ref connector-name="my-connector2"
+ backup-connector-name="my-backup-connector2"/>
+ <connector-ref connector-name="my-connector3"
+ backup-connector-name="my-backup-connector3"/>
<entries>
<entry name="ConnectionFactory"/>
</entries>
@@ -500,11 +507,15 @@
<para>If you're using JMS but you're not using JNDI then you can also specify the
list of [connector, backup connector] pairs directly when instantiating the
<literal>JBossConnectionFactory</literal>, here's an
- example:<programlisting>List<Pair<TransportConfiguration, TransportConfiguration>> serverList = new ArrayList<Pair<TransportConfiguration, TransportConfiguration>>();
+ example:<programlisting>List<Pair<TransportConfiguration, TransportConfiguration>> serverList =
+ new ArrayList<Pair<TransportConfiguration, TransportConfiguration>>();
-serverList.add(new Pair<TransportConfiguration, TransportConfiguration>(liveTC0, backupTC0));
-serverList.add(new Pair<TransportConfiguration, TransportConfiguration>(liveTC1, backupTC1));
-serverList.add(new Pair<TransportConfiguration, TransportConfiguration>(liveTC2, backupTC2));
+serverList.add(new Pair<TransportConfiguration,
+ TransportConfiguration>(liveTC0, backupTC0));
+serverList.add(new Pair<TransportConfiguration,
+ TransportConfiguration>(liveTC1, backupTC1));
+serverList.add(new Pair<TransportConfiguration,
+ TransportConfiguration>(liveTC2, backupTC2));
ConnectionFactory jmsConnectionFactory = new JBossConnectionFactory(serverList);
@@ -526,11 +537,15 @@
<para>If you're using the Core API you can also specify the list of servers directly
when creating the <literal>ClientSessionFactory</literal> instance. Here's an
example:</para>
- <programlisting>List<Pair<TransportConfiguration, TransportConfiguration>> serverList = new ArrayList<Pair<TransportConfiguration, TransportConfiguration>>();
+ <programlisting>List<Pair<TransportConfiguration, TransportConfiguration>> serverList =
+ new ArrayList<Pair<TransportConfiguration, TransportConfiguration>>();
-serverList.add(new Pair<TransportConfiguration, TransportConfiguration>(liveTC0, backupTC0));
-serverList.add(new Pair<TransportConfiguration, TransportConfiguration>(liveTC1, backupTC1));
-serverList.add(new Pair<TransportConfiguration, TransportConfiguration>(liveTC2, backupTC2));
+serverList.add(new Pair<TransportConfiguration,
+ TransportConfiguration>(liveTC0, backupTC0));
+serverList.add(new Pair<TransportConfiguration,
+ TransportConfiguration>(liveTC1, backupTC1));
+serverList.add(new Pair<TransportConfiguration,
+ TransportConfiguration>(liveTC2, backupTC2));
ClientSessionFactory factory = new ClientSessionFactoryImpl(serverList);
@@ -558,9 +573,12 @@
<programlisting><cluster-connections>
<cluster-connection name="my-explicit-cluster">
<address>jms</address>
- <connector-ref connector-name="my-connector1" backup-connector-name="my-backup-connector1"/>
- <connector-ref connector-name="my-connector2" backup-connector-name="my-backup-connector2"/>
- <connector-ref connector-name="my-connector3" backup-connector-name="my-backup-connector3"/>
+ <connector-ref connector-name="my-connector1"
+ backup-connector-name="my-backup-connector1"/>
+ <connector-ref connector-name="my-connector2"
+ backup-connector-name="my-backup-connector2"/>
+ <connector-ref connector-name="my-connector3"
+ backup-connector-name="my-backup-connector3"/>
</cluster-connection>
</cluster-connections></programlisting>
<para>The <literal>cluster-connection</literal> element can contain zero or more
@@ -588,9 +606,10 @@
Messaging can be configured to automatically <emphasis>redistribute</emphasis> messages
from queues which have no consumers back to other nodes in the cluster which do have
matching consumers.</para>
- <para>Message redistribution can be configured to kick in immediately after the last consumer
- on a queue is closed, or to wait a configurable delay after the last consumer on a queue
- is closed before redistributing. By default message redistribution is disabled.</para>
+ <para>Message redistribution can be configured to kick in immediately after the last
+ consumer on a queue is closed, or to wait a configurable delay after the last consumer
+ on a queue is closed before redistributing. By default message redistribution is
+ disabled.</para>
<para>Message redistribution can be configured on a per address basis, by specifying the
redistribution delay in the address settings, for more information on configuring
address settings please see the chapter [LINK].</para>
@@ -638,9 +657,9 @@
what other servers in the cluster it should connect to, although it is possible to
explicitly define each target server too in the cluster connection if, for example,
UDP is not available on your network.</para>
- <para>With a symmetric cluster each node knows about all the queues that exist on all the
- other nodes and what consumers they have. With this knowledge it can determine how
- to load balance and redistribute messages around the nodes.</para>
+ <para>With a symmetric cluster each node knows about all the queues that exist on all
+ the other nodes and what consumers they have. With this knowledge it can determine
+ how to load balance and redistribute messages around the nodes.</para>
<para>DIAGRAM</para>
</section>
<section>
@@ -649,10 +668,10 @@
the cluster directly, instead the nodes form a chain with a node on each end of the
chain and all other nodes just connecting to the previous and next nodes in the
chain.</para>
- <para>An example of this would be a three node chain consisting of nodes A, B and C. Node
- A is hosted in one network and has many producer clients connected to it sending
- order messages. Due to corporate policy, the order consumer clients need to be
- hosted in a different network, and that network is only accessible via a third
+ <para>An example of this would be a three node chain consisting of nodes A, B and C.
+ Node A is hosted in one network and has many producer clients connected to it
+ sending order messages. Due to corporate policy, the order consumer clients need to
+ be hosted in a different network, and that network is only accessible via a third
network. In this setup node B acts as a mediator with no producers or consumers on
it. Any order messages arriving on node A will be forwarded to node B, which will in
turn forward them to node C where they can get consumed. Node A does not need to
More information about the jboss-cvs-commits
mailing list