[jboss-cvs] JBoss Messaging SVN: r5187 - projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Oct 27 18:25:56 EDT 2008
Author: irooskov at redhat.com
Date: 2008-10-27 18:25:55 -0400 (Mon, 27 Oct 2008)
New Revision: 5187
Modified:
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Appendix.xml
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Author_Group.xml
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Book_Info.xml
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Important_Features.xml
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/JBoss_Messaging_User_Guide_CP03.xml
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/configuration.xml
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/introduction.xml
Log:
updated book with Tim's corections
Modified: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Appendix.xml
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Appendix.xml 2008-10-27 22:08:35 UTC (rev 5186)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Appendix.xml 2008-10-27 22:25:55 UTC (rev 5187)
@@ -6,8 +6,5 @@
<appendixinfo>
<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</appendixinfo>
- <title>Revision History</title>
- <para>
- </para>
</appendix>
Modified: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Author_Group.xml
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Author_Group.xml 2008-10-27 22:08:35 UTC (rev 5186)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Author_Group.xml 2008-10-27 22:25:55 UTC (rev 5187)
@@ -3,9 +3,12 @@
]>
<authorgroup>
-<author><firstname>Contributors: Tim Fox, Jeff Mesnil,
- Andy Taylor, Clebert Suconic, Ovidiu Feodorov, Sergey Koshcheyev,
+<author><firstname>Permanent Team: Tim Fox, Jeff Mesnil,
+ Andy Taylor, Clebert Suconic.</firstname></author>
+<author><firstname>Contributors: Ovidiu Feodorov, Sergey Koshcheyev,
Ron Sigal, Madhu Konda, Jay Howell, Tyronne Wickramarathne, Aaron Walker,
Adrian Brock, Rajdeep Dua, Tom Elrod, Alex Fu, Juha Lindfors, Alexey
- Loubyansky, Luc Texier, Scott Stark, Aslak Knutsen, Mark Little and Pete Bennett</firstname></author>
+ Loubyansky, Luc Texier, Scott Stark, Aslak Knutsen</firstname></author>
+<author><firstname>Messaging support team: Jay Howell, David Boeren, Mike Clark, Tyronne Wickramarathne</firstname></author>
+<author><firstname>Other thanks to: Mark Little and Pete Bennett</firstname></author>
</authorgroup>
Modified: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Book_Info.xml
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Book_Info.xml 2008-10-27 22:08:35 UTC (rev 5186)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Book_Info.xml 2008-10-27 22:25:55 UTC (rev 5187)
@@ -4,7 +4,7 @@
<bookinfo id="JBoss_Messaging_User_Guide-Product_Name_and_Version">
<title>JBoss Messaging User Guide CP03</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.3 Cummulative Patch 3</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 3</subtitle>
<edition>1.0</edition>
<pubsnumber>4</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
Modified: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Important_Features.xml
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Important_Features.xml 2008-10-27 22:08:35 UTC (rev 5186)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/Important_Features.xml 2008-10-27 22:25:55 UTC (rev 5187)
@@ -19,7 +19,7 @@
</itemizedlist>
</para>
</section>
- <section id="JBoss_Messaging_Features">
+<!-- <section id="JBoss_Messaging_Features">
<title>JBoss Messaging Features</title>
<para>
JBoss Messaging implements a high-performance and robust messaging core that is designed to support the largest and most heavily utilized Service Oriented Architectures(SOAs), Enterprise Service Buses (ESBs) and other integration needs ranging from the simplest to the highest demand networks.
@@ -85,7 +85,7 @@
</listitem>
</itemizedlist>
</para>
- </section>
+ </section> -->
<section id="clustering">
<title>Clustering Features</title>
<formalpara>
Modified: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/JBoss_Messaging_User_Guide_CP03.xml
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/JBoss_Messaging_User_Guide_CP03.xml 2008-10-27 22:08:35 UTC (rev 5186)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/JBoss_Messaging_User_Guide_CP03.xml 2008-10-27 22:25:55 UTC (rev 5187)
@@ -4,9 +4,9 @@
<book>
<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="About_This_Book.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+<!-- <xi:include href="About_This_Book.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
<xi:include href="introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Important_Features.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+<!-- <xi:include href="Important_Features.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
<!-- <xi:include href="gettingstarted.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
<xi:include href="runningexamples.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
Modified: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/configuration.xml
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/configuration.xml 2008-10-27 22:08:35 UTC (rev 5186)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/configuration.xml 2008-10-27 22:25:55 UTC (rev 5187)
@@ -1036,9 +1036,9 @@
The example <filename>mysql-persistence-service.xml</filename>,
<filename>ndb-persistence-service.xml</filename>,
<filename>oracle-persistence-service.xml</filename>,
- <filename>postgres-persistence-service.xml</filename> and
- <filename>sybase-persistence-service.xml</filename> and
- <filename>mssql-persistence-service.xml</filename> configuration files are
+ <filename>postgres-persistence-service.xml</filename>,
+ <filename>sybase-persistence-service.xml</filename>,
+ <filename>mssql-persistence-service.xml</filename> and <filename>db2-persistence-service.xml</filename> configuration files are
available in the <filename>examples/config</filename> directory of the
release bundle.</para>
Modified: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/introduction.xml
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/introduction.xml 2008-10-27 22:08:35 UTC (rev 5186)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/introduction.xml 2008-10-27 22:25:55 UTC (rev 5187)
@@ -19,31 +19,6 @@
standards-based format as well as being designed to be able to support other
messaging protocols in the future.</para>
- <para>JBoss Messaging is destined to become an integral part of the JBoss
- Enterprise Application Platform, and the new Service Integration
- Platform.</para>
-
- <para>Currently it is available for embedded use within the JBoss
- Application Server 4.2.0.GA or later (JBossAS). Work to integrate JBoss
- Messaging with the new JBoss Microcontainer is under way.</para>
-
- <para>JBoss Messaging is also an integral part of Red Hat's strategy for
- messaging. JBoss Messaging is committed to AMQP ( <ulink
- url="http://www.amqp.org">AMQP</ulink>)- the new messaging standard from Red
- Hat and others. Later versions of JBoss Messaging will support AMQP, and
- JBoss Messaging will be focussed on becoming the premier AMQP Java
- broker.</para>
-
- <section id="support">
- <title>JBoss Messaging support cover from Red Hat</title>
-
- <para>JBoss Messaging is part of JBoss Application Server Integration
- Platform (JBoss EAP 4.3) and it is already the default JMS provider on
- JBoss AS 5 (under Beta release at this current time).Production support is
- already available through JBoss EAP 4.3, and we offer developer support
- for JBoss 4.2.x.</para>
- </section>
-
<section id="features">
<title>JBoss Messaging Features</title>
@@ -191,7 +166,57 @@
</listitem>
</itemizedlist>
</section>
-
+ <section id="clustering">
+ <title>Clustering Features</title>
+ <formalpara>
+ <title>Fully clustered queues and topics</title>
+ <para>
+ "Logical" queues and topics are distributed across the cluster. You can send to a queue or a topic from any node, and receive from any other.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Fully clustered durable subscriptions</title>
+ <para>
+ A particular durable subscription can be accessed from any node of the cluster - allowing you to spread processing load from that subscription across the cluster.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Fully clustered temporary queues</title>
+ <para>
+ Send a message with a <literal>replyTo</literal> of a temp queue and it can be sent back on any node of the cluster.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Intelligent message redistribution</title>
+ <para>
+ Messages are automatically moved between different nodes of the cluster if consumers are faster on one node than another. This can help prevent starvation or build up of messages on particular nodes.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Message order protection</title>
+ <para>
+ If you want to ensure that the order of messages produced by a producer is the same as is consumed by a consumer then you can set this to true. This works even in the presence of message redistribution.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Fully transparent failover</title>
+ <para>
+ When a server fails, your sessions continue without exceptions on a new node as if nothing happened. (Fully configurable - If you don't want this you can fall back to exceptions being thrown and manually recreation of connections on another node)
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>High availability and seamless fail-over</title>
+ <para>
+ 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>
+ </formalpara>
+ <formalpara>
+ <title>Message bridge</title>
+ <para>
+ JBoss Messaging contains a message bridge component which enables you to bridge messages between any two JMS1.1 destinations on the same or physical separate locations. (E.g. separated by a WAN). This allows you to connect geographically separate clusters, forming huge globally distributed logical queues and topics.
+ </para>
+ </formalpara>
+ </section>
<section id="compatibility">
<title>Compatibility with JBossMQ</title>
@@ -212,5 +237,28 @@
identical, so they will require some simple adjustments to get them to work with JBoss Messaging. Also, the database data model is completely different, so don't attempt to use JBoss Messaging with a JBoss MQ data schema and vice-versa. </para>
</important>
+ <note>
+ <para>
+ JBoss Messaging is built against the JBoss AS 4.2 libraries which are built using Java 5. Therefore JBoss Messaging only runs with Java 5 or later.
+ </para>
+ </note>
</section>
+ <section id="Limitations_of_JBossMQ">
+ <title>Limitations of JBossMQ</title>
+ <para>
+ JBossMQ has two fundamental limitations:
+ <itemizedlist>
+ <listitem>
+ <para>
+ JBossMQ is based on SpyderMQ (the open source project) which is a non-clustered broker.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The threading model and the overall design of the non-clustered broker leads to performance limitations in certain high load usage scenarios.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </section>
</chapter>
\ No newline at end of file
More information about the jboss-cvs-commits
mailing list