[jboss-cvs] JBoss Messaging SVN: r2512 - trunk/docs/userguide-2/en/modules.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Feb 28 22:37:49 EST 2007
Author: sam.griffith at jboss.com
Date: 2007-02-28 22:37:49 -0500 (Wed, 28 Feb 2007)
New Revision: 2512
Modified:
trunk/docs/userguide-2/en/modules/CLUST_about.xml
trunk/docs/userguide-2/en/modules/CLUST_configuration.xml
trunk/docs/userguide-2/en/modules/CLUST_installation.xml
trunk/docs/userguide-2/en/modules/CLUST_introduction.xml
trunk/docs/userguide-2/en/modules/CLUST_overview.xml
trunk/docs/userguide-2/en/modules/UG2_about.xml
trunk/docs/userguide-2/en/modules/UG2_introduction.xml
Log:
Updates
Modified: trunk/docs/userguide-2/en/modules/CLUST_about.xml
===================================================================
--- trunk/docs/userguide-2/en/modules/CLUST_about.xml 2007-03-01 02:15:27 UTC (rev 2511)
+++ trunk/docs/userguide-2/en/modules/CLUST_about.xml 2007-03-01 03:37:49 UTC (rev 2512)
@@ -1,26 +1,19 @@
-<chapter id="about">
+<chapter id="CLUST_about">
- <title>JBoss Messaging Clustering Introduction</title>
+<title>JBoss Messaging Clustering</title>
- <para>
- This guide gives a brief overview of the features available in JBoss Messaging Clustering 1.2.0.CR1
- </para>
+ <para>
+ This section of the userguide gives a brief overview of the features available in JBoss Messaging Clustering 2.0
+ </para>
- <para>
- It also gives a high level explanation of how clustering works and shows you how to set up a simple
- cluster of JBoss Messaging servers.
- </para>
+ <para>
+ It gives a high level explanation of how clustering works and shows you how to set up a simple
+ cluster of JBoss Messaging servers.
+ </para>
- <para>
- This guide is work in progress.
- </para>
+ <para>
+ Please send your suggestions, updates or comments to the
+ <ulink url="http://www.jboss.org/index.html?module=bb&op=viewforum&f=238">JBoss Messaging user forum</ulink>.
+ </para>
- <para>It will expand considerably for the 1.2.0 GA release.
- </para>
-
- <para>
- Please send your suggestions or comments to the
- <ulink url="http://www.jboss.org/index.html?module=bb&op=viewforum&f=238">JBoss Messaging user forum</ulink>.
- </para>
-
</chapter>
Modified: trunk/docs/userguide-2/en/modules/CLUST_configuration.xml
===================================================================
--- trunk/docs/userguide-2/en/modules/CLUST_configuration.xml 2007-03-01 02:15:27 UTC (rev 2511)
+++ trunk/docs/userguide-2/en/modules/CLUST_configuration.xml 2007-03-01 03:37:49 UTC (rev 2512)
@@ -1,4 +1,4 @@
-<chapter id="configuration">
+<chapter id="CLUST_configuration">
<title>JBoss Messaging Clustering Configuration</title>
Modified: trunk/docs/userguide-2/en/modules/CLUST_installation.xml
===================================================================
--- trunk/docs/userguide-2/en/modules/CLUST_installation.xml 2007-03-01 02:15:27 UTC (rev 2511)
+++ trunk/docs/userguide-2/en/modules/CLUST_installation.xml 2007-03-01 03:37:49 UTC (rev 2512)
@@ -1,4 +1,4 @@
-<chapter id="installation">
+<chapter id="CLUST_installation">
<title>JBoss Messaging Clustering Installation</title>
Modified: trunk/docs/userguide-2/en/modules/CLUST_introduction.xml
===================================================================
--- trunk/docs/userguide-2/en/modules/CLUST_introduction.xml 2007-03-01 02:15:27 UTC (rev 2511)
+++ trunk/docs/userguide-2/en/modules/CLUST_introduction.xml 2007-03-01 03:37:49 UTC (rev 2512)
@@ -1,4 +1,4 @@
-<chapter id="introduction">
+<chapter id="CLUST_introduction">
<title>Introduction</title>
@@ -8,8 +8,8 @@
</para>
<para>
It will allow you to smoothly distribute your application load across your cluster,
- intelligently balancing and utilising each nodes CPU cycles, with no single point of failure,
- providing a highly scalable and performant clustering implementation.
+ intelligently balancing and utilizing each nodes CPU cycles, with no single point of failure,
+ providing a highly scalable and perform-ant clustering implementation.
</para>
<section id="c_features">
Modified: trunk/docs/userguide-2/en/modules/CLUST_overview.xml
===================================================================
--- trunk/docs/userguide-2/en/modules/CLUST_overview.xml 2007-03-01 02:15:27 UTC (rev 2511)
+++ trunk/docs/userguide-2/en/modules/CLUST_overview.xml 2007-03-01 03:37:49 UTC (rev 2512)
@@ -1,4 +1,4 @@
-<chapter id="overview">
+<chapter id="CLUST_overview">
<title>Clustering overview</title>
@@ -6,7 +6,7 @@
<title>JBoss Messaging Clustering Overview</title>
<para>
- Here's a brief overview of how clustering works in JBoss Messaging 1.2.
+ Here's a brief overview of how clustering works in JBoss Messaging 2.0.
</para>
<para>As mentioned in the previous chapter, please note that not all this functionality is
@@ -100,7 +100,7 @@
<para>
JBoss Messaging deals with this problem by intelligently pulling messages from other less
- busy nodes, if it detects idle consumers on the fast node and slow consumers
+ busy nodes, if it detects idle consumers on the fast node and slow consumers
on another node.
</para>
@@ -113,7 +113,7 @@
Normally, persistent messages are persisted in a shared database which is shared by all nodes
in the cluster.
- JBoss Messaging 1.2.GA will contain
+ JBoss Messaging 2.0.GA will contain
an option where you can choose to not persist persistent messages in a database, but instead to replicate them between nodes of the cluster.
</para>
@@ -127,10 +127,8 @@
</para>
<para>
- If the messages are replicated onto suffficient nodes and the hardware is set-up with UPS, then we believe a comparable reliability guarantee to persisting messages to disk
- can be achieved.
-
- Of course, this won't be suitable for all situations, but you use the best tool for the job.
+ If the messages are replicated onto sufficient nodes and the hardware is set-up with UPS, then we believe a comparable reliability guarantee to persisting messages to disk
+ can be achieved. Of course, this won't be suitable for all situations, but you use the best tool for the job.
</para>
</section>
Modified: trunk/docs/userguide-2/en/modules/UG2_about.xml
===================================================================
--- trunk/docs/userguide-2/en/modules/UG2_about.xml 2007-03-01 02:15:27 UTC (rev 2511)
+++ trunk/docs/userguide-2/en/modules/UG2_about.xml 2007-03-01 03:37:49 UTC (rev 2512)
@@ -1,15 +1,14 @@
<chapter id="UG2_about">
- <title>Introducing JBoss Messaging</title>
+ <title>Introducing JBoss Messaging Release 2.0</title>
<para>JBoss Messaging is a high performance JMS provider in the JBoss Enterprise Middleware Stack (JEMS). It is a complete rewrite of JBossMQ, which is the current default JMS provider in JBoss AS 4.x. JBoss Messaging will be the default JMS provider in JBoss AS 5.x and later, and it is the backbone of the JBoss ESB infrastructure.</para>
- <para>Compared with JBossMQ, JBoss Messaging offers vastly improved performance in both single node and clustered environments. Please see <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingPerformanceResultsPre1_0">this wiki page</ulink> for performance benchamrks and <xref linkend="performance"/> on how to generate your own performance benchmarks. It also features a much better internal architecture that would allow us to add more features in the future.</para>
+ <para>Compared with JBossMQ, JBoss Messaging offers vastly improved performance in both single node and clustered environments. Please see <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingPerformanceResultsPre1_0">this wiki page</ulink> for performance benchmarks and <xref linkend="UG2_performance"/> on how to generate your own performance benchmarks. It also features a much better internal architecture that would allow us to add more features in the future.</para>
<para>While JBoss Messaging only becomes the default JMS provider from JBoss AS 5.x, production users on JBoss AS 4.x can still take advantage of the performance improvements by easily replacing the JBossMQ module with JBoss Messaging.</para>
<para>In this guide, we discuss how to install and use JBoss Messaging in JBoss 4.x production servers. We cover JBoss Messaging-specific configuration options, as well as how to run the build-in sanity / performance tests.</para>
-
<para>
This guide is work in progress. Please send your suggestions or comments to the
Modified: trunk/docs/userguide-2/en/modules/UG2_introduction.xml
===================================================================
--- trunk/docs/userguide-2/en/modules/UG2_introduction.xml 2007-03-01 02:15:27 UTC (rev 2511)
+++ trunk/docs/userguide-2/en/modules/UG2_introduction.xml 2007-03-01 03:37:49 UTC (rev 2512)
@@ -11,9 +11,11 @@
JBoss Messaging implements a high performance, robust messaging core that is designed to
support the largest and most heavily utilized SOAs, enterprise service buses (ESBs) and other
integration needs ranging from the simplest to the highest demand networks.
- JBoss Messaging includes a JMS front-end to deliver messaging in a standards-based format.
- Additionally, the JBoss Messaging core is also designed to be able to support other messaging
- protocols in the future.
+ It will allow you to smoothly distribute your application load across your cluster,
+ intelligently balancing and utilizing each nodes CPU cycles, with no single point of failure,
+ providing a highly scalable and perform-ant clustering implementation. JBoss Messaging includes
+ a JMS front-end to deliver messaging in a standards-based format as well as being designed to be
+ able to support other messaging protocols in the future.
</para>
<para>
@@ -38,7 +40,7 @@
<section id="features">
- <title>JBoss Messaging 1.0.1 Features</title>
+ <title>JBoss Messaging 1.2.0.GA Features</title>
<para>
JBoss Messaging provides:
@@ -61,7 +63,7 @@
</listitem>
<listitem>
<para>
- A foundation for JBoss ESB for SOA initiatives; JBoss ESB, due in late 2006, will use
+ A foundation for JBoss ESB for SOA initiatives; JBoss ESB uses
JBoss Messaging as its foundation.
</para>
</listitem>
@@ -92,6 +94,11 @@
Distributed, transactional and reliable
</para>
</listitem>
+ <listitem>
+ <para>
+ Clustering support
+ </para>
+ </listitem>
</itemizedlist>
</listitem>
@@ -138,6 +145,73 @@
</para>
</listitem>
</itemizedlist>
+
+ <para>
+ JBoss Messaging 1.2 GA Clustering provides the following features:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ Distributed queues. Messages sent to a distributed queue while attached to a
+ particular node will be routed to a queue instance on a particular node according
+ to a routing policy.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Distributed topics. Messages sent to a distributed topic while attached at a
+ particular node will be received by subscriptions on other nodes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Fully reliable message distribution. Once and only once delivery is fully guaranteed.
+ When sending messages to a topic with multiple durable subscriptions
+ across a cluster we guarantee that message reaches all the subscriptions
+ (or none of them in case of failure).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Persistent level reliability guarantee without persistence! By replicating persistent
+ messages between nodes in memory, we can obtain comparable reliability levels to persisting
+ messages to disk, without actually storing them to disk.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Pluggable routing implementation. The policy for routing messages to a queue is fully
+ pluggable and easily replaceable. The default policy always chooses a queue at the local
+ node if there is one, and if not, it round robins between queues on different nodes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Intelligent message redistribution policy. Messages are automatically distributed between
+ nodes depending on how fast or slow consumers are on certain nodes. If there are no or slow
+ consumers on a particular queue node, messages will be pulled from that queue to a queue with
+ faster consumers on a different node. The policy is fully pluggable.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Shared durable subscriptions. Consumers can connect to the same durable subscription while
+ attached to different nodes. This allows processing load from durable subscriptions to be
+ distributed across the cluster in a similar way to queues.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ High availability and seamless fail-over. If the node you are connected to fails, you
+ will automatically fail over to another node and will not lose any persistent messages.
+ You can carry on with your session seamlessly where you left off. Once and only once
+ delivery of persistent messages is respected at all times.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+
</section>
More information about the jboss-cvs-commits
mailing list