[jboss-cvs] JBoss Messaging SVN: r4314 - in trunk: docs/userguide/en/modules and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed May 28 00:37:34 EDT 2008
Author: clebert.suconic at jboss.com
Date: 2008-05-28 00:37:33 -0400 (Wed, 28 May 2008)
New Revision: 4314
Modified:
trunk/
trunk/docs/userguide/en/modules/about.xml
trunk/docs/userguide/en/modules/introduction.xml
trunk/docs/userguide/en/modules/journal.xml
trunk/docs/userguide/en/modules/troubleshooting.xml
Log:
Few documentation changes
Property changes on: trunk
___________________________________________________________________
Name: svn:ignore
- output
thirdparty
messaging.iws
bin
ObjectStore
build
data
eclipse-output
+ output
thirdparty
messaging.iws
bin
ObjectStore
build
data
eclipse-output
logs
Modified: trunk/docs/userguide/en/modules/about.xml
===================================================================
--- trunk/docs/userguide/en/modules/about.xml 2008-05-28 04:23:16 UTC (rev 4313)
+++ trunk/docs/userguide/en/modules/about.xml 2008-05-28 04:37:33 UTC (rev 4314)
@@ -1,11 +1,9 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="about">
<title>About JBoss Messaging 2.0.0</title>
- <para>JBoss Messaging is the enterprise messaging system from JBoss.</para>
- <para>JBoss Messaging is the default JMS provider in the
- JBoss Enterprise Application Platform, and JBoss Service Integration
- Platform. It will also be the default JMS provider in JBoss Application
- Server 5, and is the default JMS provider for JBoss ESB.</para>
+ <para>JBoss Messaging 2 is the next level of messaging system being developed by JBoss, designed to attend very large demanding system and so we really believe JBoss Messaging 2 will be the most performatic
+ Messaging System written in Java available on the market.</para>
+ <para>JBoss Messaging 1.4 has been the default implementation on JBoss Service Integration Platform and JBoss 5 for some time already. </para>
<para>JBoss Messaging is an integral part of Red Hat's strategy for
messaging.</para>
<para>The procedure of installing and configuring JBoss Messaging is detailed in this guide, along with a set of
Modified: trunk/docs/userguide/en/modules/introduction.xml
===================================================================
--- trunk/docs/userguide/en/modules/introduction.xml 2008-05-28 04:23:16 UTC (rev 4313)
+++ trunk/docs/userguide/en/modules/introduction.xml 2008-05-28 04:37:33 UTC (rev 4314)
@@ -46,7 +46,8 @@
<itemizedlist>
<listitem>
- <para>Journal based persistence. todo</para>
+ <para>Journal based persistence.</para>
+ <para>An append only file system where messages and transactions are stored at a high performance rate. We don't even need an external database for that.</para>
</listitem>
<listitem>
@@ -57,11 +58,14 @@
</listitem>
<listitem>
- <para>Native io. todo</para>
+ <para>Asynchronous IO (Linux only at the moment)</para>
+ <para>Instead of syncing the disk and waiting slow IO operations to complete during transactions, we can submit the writes directly on the kernel and get a notification when it is complete.
+ With this design we can support very high transaction rates even on very short transactions containing just few messages or acknowledgements. </para>
</listitem>
<listitem>
- <para>Standalone and embedded versions. todo</para>
+ <para>Standalone and embedded versions.</para>
+ <para>You can embed JBoss Messaging at your own system without the requirement of any servers at all. Just instantiate few POJOS and you have a Messaging System running.</para>
</listitem>
</itemizedlist>
@@ -119,10 +123,10 @@
<para>Extensive JMX management interface</para>
</listitem>
- <listitem>
+ <!-- <listitem>
<para>Support for most major databases including Oracle, Sybase,
MS SQL Server, PostgreSQL and MySQL</para>
- </listitem>
+ </listitem> -->
<listitem>
<para>HTTP transport to allow use through firewalls that only
@@ -144,10 +148,10 @@
subscriptions</para>
</listitem>
- <listitem>
+ <!-- <listitem>
<para>Automatic paging of messages to storage. Allows the use of
very large queues - too large to fit in memory at once</para>
- </listitem>
+ </listitem> -->
</itemizedlist>
<!-- <para>Clustering features:</para>
Modified: trunk/docs/userguide/en/modules/journal.xml
===================================================================
--- trunk/docs/userguide/en/modules/journal.xml 2008-05-28 04:23:16 UTC (rev 4313)
+++ trunk/docs/userguide/en/modules/journal.xml 2008-05-28 04:37:33 UTC (rev 4314)
@@ -3,14 +3,19 @@
<title>The journal based persistence approach</title>
<section id="journal.asyncio">
<title>ASYNCIO</title>
- <para>todo</para>
+ <para>If you are using JBoss Messaging 2 on a Linux system, you can take full advantage of this feature. All you have to do is to make sure libaio is installed and you are using ext3 or ext2 or newer kernels.</para>
+ <para>Instead of synchronizing the whole disk on every commit required by the journal, We submit writes directly to the kernel and we get callbacks when the information is stored on the hard drive. With that
+ we maximize performance by one transaction not affecting other transaction's and using Direct Memory Access between the Journal and the Kernel. With AIO you can have high rate transactions even when you commit several small transactions.
+ We are planing migrating this native liraries to other platforms besides Linux, as other OS's will have different options for Asynchronous IO.</para>
</section>
<section id="journal.nio">
<title>NIO</title>
- <para>todo</para>
+ <para>Even though AIO takes a lot of advantage of the Linux Kernel specific features, NIO is not bad on performance at all.</para>
+ <para>In fact both NIO and AIO journals share a lot of its implementation on an abstract class and we have verified that even our Journal with NIO is performing better than our competition.</para>
</section>
<section id="journal.jdbc">
<title>JDBC</title>
- <para>todo</para>
+ <para>We are not supporting any JDBC mapping on JBoss Messaging 2 Alpha. JDBC is planned for Beta for users that require a database for management purposes.
+ We will of course optimize JDBC access but we won't expect a lot of performance for persistent messages on JDBC as a relational database wasn't designed to the demand levels required by a Messaging System.</para>
</section>
</chapter>
\ No newline at end of file
Modified: trunk/docs/userguide/en/modules/troubleshooting.xml
===================================================================
--- trunk/docs/userguide/en/modules/troubleshooting.xml 2008-05-28 04:23:16 UTC (rev 4313)
+++ trunk/docs/userguide/en/modules/troubleshooting.xml 2008-05-28 04:37:33 UTC (rev 4314)
@@ -1,4 +1,47 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="troubleshooting">
<title>Troubleshooting</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>Message on logs: AIO wasn't located on this platform</para>
+ <para>Possible causes are:
+ <itemizedlist>
+ <listitem>
+ <para>Linux is not your platform</para>
+ <para>Solution: Just ignore the message as NIO will be selected automatically or change the journal type to NIO on jbm-configuration.xml</para>
+ </listitem>
+ <listitem>
+ <para>The JBoss Messaging JNI wrapper is not on library.path</para>
+ <para>Solution: Make sure you have libJBMLibAIO32.so or libJBMLibAIO64.so as provided on the download package.</para>
+ </listitem>
+ <listitem>
+ <para>libaio is not installed</para>
+ <para>Solution: Make sure you have libaio installed at your Linux distribution. This could be done as yum install libaio on Fedora. (Refer to your manual to how to upgrade or install packages)</para>
+ </listitem>
+ <listitem>
+ <para>libaio is very old</para>
+ <para>Solution: We have been using and testing libaio 0.3.106 and Kernel 2.6. If you have older versions you might need to update or change the journal type to NIO on jbm-configuration.xml</para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Low response time even though the CPU and IO seems ok</para>
+ <para>Possible causes are:
+ <itemizedlist>
+ <listitem>
+ <para>You are using short transactions in your system and you don't have TCPNoDelay set</para>
+ <para>Make sure you have remoting-tcp-nodelay set to true on jbm-configuration.xml</para>
+ </listitem>
+ <listitem>
+ <para>The journal directory is a Network Disk</para>
+ <para>You shouldn't use a journal over a network storage.</para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+
</chapter>
\ No newline at end of file
More information about the jboss-cvs-commits
mailing list