[jboss-cvs] JBoss Messaging SVN: r8003 - projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Apr 12 00:16:23 EDT 2010
Author: rebecca.newton
Date: 2010-04-12 00:16:22 -0400 (Mon, 12 Apr 2010)
New Revision: 8003
Added:
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Running_HQ.xml
Removed:
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Running_JBM.xml
Modified:
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Examples.xml
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Installation.xml
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Introduction.xml
Log:
Updated file name for Running HornetQ chapter.
Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Examples.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Examples.xml 2010-04-12 02:57:09 UTC (rev 8002)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Examples.xml 2010-04-12 04:16:22 UTC (rev 8003)
@@ -7,7 +7,7 @@
<itemizedlist>
<listitem>
<para>
- <emphasis>JMS Examples</emphasis>, which demonstrate functionality by sending and consuming JMS messages.
+ <emphasis>HornetQ Examples</emphasis>, which demonstrate functionality by sending and consuming HornetQ messages.
</para>
</listitem>
<listitem>
@@ -20,9 +20,9 @@
All examples are run with <application>Apache Ant</application>. Ant must be installed on your system and the Ant <filename>bin</filename> directory must be included in your filepath.
</para>
<section id="examples.jms">
- <title>The JMS Examples</title>
+ <title>The HornetQ Examples</title>
<para>
- The JMS Examples follow the same format. Each example has its own directory, which contains the following:
+ The HornetQ examples follow the same format. Each example has its own directory, which contains the following:
</para>
<variablelist>
<varlistentry>
@@ -54,7 +54,7 @@
Each example starts one or more standalone servers, and stops them after the example has completed.
</para>
<para>
- For this Quickstart Guide, we will run the Queue Example. For all other examples, refer to the JBoss Messaging User Guide.
+ For this Quickstart Guide, we will run the Queue Example. For all other examples, refer to the HornetQ User Guide.
</para>
<section id="examples.jms.queue">
<title>Running the Queue Example</title>
@@ -71,57 +71,57 @@
init:
compile:
- [echo] src.example.dir=/home/andy/projects/JBMTrunk/examples/jms/queue/src
- [javac] Compiling 5 source files to /home/andy/projects/JBMTrunk/examples/jms/queue
+ [echo] src.example.dir=/home/andy/projects/JBMTrunk/examples/jms/queue/src
+ [javac] Compiling 5 source files to /home/andy/projects/JBMTrunk/examples/jms/queue
/build/classes
runExample:
- [java] 10:41:04,149 INFO @main [JMSExample] jbm.example.runServer is true
- [java] 10:41:04,149 INFO @main [JMSExample] starting server with config 'server0'
+ [java] 10:41:04,149 INFO @main [JMSExample] jbm.example.runServer is true
+ [java] 10:41:04,149 INFO @main [JMSExample] starting server with config 'server0'
logServerOutput true
- [java] 10:41:04,149 INFO @main [JMSExample] and vm args: -Xms512M,-Xmx512M,-XX:+U
+ [java] 10:41:04,149 INFO @main [JMSExample] and vm args: -Xms512M,-Xmx512M,-XX:+U
seParallelGC,-XX:+AggressiveOpts,-XX:+UseFastAccessorMethods,-Djava.util.logging.config.
file=/home/andy/projects/JBMTrunk/examples/jms/common/../../../src/config/stand-alone/no
n-clustered/logging.properties
- [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:08,437 INFO @main [Journal
+ [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:08,437 INFO @main [Journal
StorageManager] AIO journal selected
- [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:08,437 WARN @main [Journal
+ [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:08,437 WARN @main [Journal
StorageManager] AIO wasn't located on this platform, it will fall back to using pure Jav
a NIO. If your platform is Linux, install LibAIO to enable the AIO journal
- [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:08,437 WARN @main [Securit
+ [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:08,437 WARN @main [Securit
yStoreImpl] It has been detected that the cluster admin password which is used to replic
ate management operation from one node to the other has not had its password changed fro
m the installation default. Please see the JBoss Messaging user guide for instructions o
n how to do this.
- [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:10,941 INFO @main [JBossCo
+ [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:10,941 INFO @main [JBossCo
nnectionFactory] read only is false
- [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:10,941 INFO @main [JBossCo
+ [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:10,941 INFO @main [JBossCo
nnectionFactory] read only is false
- [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:10,941 INFO @main [JBossCo
+ [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:10,941 INFO @main [JBossCo
nnectionFactory] read only is false
- [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:10,991 WARN @main [JMSServ
+ [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:10,991 WARN @main [JMSServ
erManagerImpl] Binding for java:/ConnectionFactory already exists
- [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:10,991 WARN @main [JMSServ
+ [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:10,991 WARN @main [JMSServ
erManagerImpl] Binding for java:/XAConnectionFactory already exists
- [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:11,241 INFO @main [Messagi
+ [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:11,241 INFO @main [Messagi
ngServerImpl] JBoss Messaging Server version 2.0.0.BETA1-SNAPSHOT (Stilton, 101) started
- [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:11,241 INFO @main [JBMBoot
+ [java] org.jboss.jms.example.SpawnedJMSServer out:10:41:11,241 INFO @main [JBMBoot
strapServer] JBoss Messaging server started
- [java] org.jboss.jms.example.SpawnedJMSServer out:STARTED::
- [java] 10:41:11,276 INFO @main [JMSExample] using server0/client-jndi.properties f
+ [java] org.jboss.jms.example.SpawnedJMSServer out:STARTED::
+ [java] 10:41:11,276 INFO @main [JMSExample] using server0/client-jndi.properties f
or jndi
- [java] Sent message: This is a text message
- [java] Received message: This is a text message
- [java]
- [java] #####################
- [java] ### SUCCESS! ###
- [java] #####################
+ [java] Sent message: This is a text message
+ [java] Received message: This is a text message
+ [java]
+ [java] #####################
+ [java] ### SUCCESS! ###
+ [java] #####################
BUILD SUCCESSFUL
Total time: 13 seconds
</programlisting>
<para>
- You have just successfully run your first JBoss Messaging example. We highly recommend trying the rest, to familiarize yourself with JBoss Messaging operations.
+ You have just successfully run your first HornetQ example. We highly recommend trying the rest, to familiarize yourself with HornetQ operations.
</para>
</section>
</section>
@@ -131,7 +131,7 @@
The Java EE Examples require an application server. Follow the instructions in the previous chapters to install your application server, if you have not already done so.
</para>
<para>
- For this Quickstart Guide, we will take you through the MDB Example. For all other examples, refer to the JBoss Messaging User Guide.
+ For this Quickstart Guide, we will take you through the MDB Example. For all other examples, refer to the HornetQ User Guide.
</para>
<important>
<title>Start your server</title>
@@ -247,7 +247,7 @@
ejbName: MessageMDBExample
</screen>
<para>
- You have now successfully deployed and run a Java EE example. We strongly recommend running other examples to familiarize yourself with JBoss Messaging operations.
+ You have now successfully deployed and run a Java EE example. We strongly recommend running other examples to familiarize yourself with HornetQ operations.
</para>
</section>
</chapter>
Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Installation.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Installation.xml 2010-04-12 02:57:09 UTC (rev 8002)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Installation.xml 2010-04-12 04:16:22 UTC (rev 8003)
@@ -2,20 +2,20 @@
<chapter id="installation">
<title>Installation</title>
<para>
- This chapter shows you how to install JBoss Messaging 2.0.
+ This chapter shows you how to install HornetQ.
</para>
<section id="installation.prerequisites">
<title>Prerequisites</title>
<note>
<para>
- JBoss Messaging 2.0 runs on Java 5 or later. We highly recommend using Java 6.
+ HornetQ runs on Java 5 or later. We highly recommend using Java 6.
</para>
</note>
<para>
- By default, the JBoss Messaging server runs with 1 gigabyte of memory. If this amount of memory is not available, modify the value in <filename>bin/run.sh</filename> accordingly.
+ By default, the HornetQ server runs with 1 gigabyte of memory. If this amount of memory is not available, modify the value in <filename>bin/run.sh</filename> accordingly.
</para>
<para>
- JBoss Messaging uses its own fast journal file for persistence. You can configure this file to use <literal>libaio</literal> (the Linux default) or Java NIO (Non-blocking Input/Output). The <literal>libaio</literal> module must be installed separately before you can use it with JBoss Messaging.
+ HornetQ uses its own fast journal file for persistence. You can configure this file to use <literal>libaio</literal> (the Linux default) or Java NIO (Non-blocking Input/Output). The <literal>libaio</literal> module must be installed separately before you can use it with HornetQ.
</para>
<para>
To install <literal>libaio</literal> using <application>yum</application>, run:
@@ -28,46 +28,46 @@
</para>
<programlisting>sudo apt-get install libaio</programlisting>
<para>
- You will require <ulink url="http://ant.apache.org/">Apache Ant</ulink> to create profiles for JBoss Application Server 5.0 and to run the JBoss Messaging examples.
+ You will require <ulink url="http://ant.apache.org/">Apache Ant</ulink> to create profiles for JBoss Application Server 5.0 and to run the HornetQ examples.
</para>
</section>
<section id="installation.standalone">
- <title>Standalone JBoss Messaging Server</title>
+ <title>Standalone HornetQ</title>
<para>
When you have downloaded the distribution, unzip it into your chosen directory. You should be able to run the distribution immediately (see <xref linkend="running.standalone" />). The directory structure is as follows:
</para>
<programlisting>
- |-- bin
- |-- config
- | |-- jboss-as
- | `-- stand-alone
- |-- docs
- | |-- api
- | |-- quickstart-guide
- | `-- user-manual
- |-- examples
- | |-- core
- | |-- javaee
- | `-- jms
- |-- lib
- |-- licenses
- `-- schemas
+ |-- bin
+ |-- config
+ | |-- jboss-as
+ | `-- stand-alone
+ |-- docs
+ | |-- api
+ | |-- quickstart-guide
+ | `-- user-manual
+ |-- examples
+ | |-- core
+ | |-- javaee
+ | `-- jms
+ |-- lib
+ |-- licenses
+ `-- schemas
</programlisting>
<itemizedlist>
<listitem>
<para>
- <filename>bin</filename> — contains the binaries and scripts required to run JBoss Messaging.
+ <filename>bin</filename> — contains the binaries and scripts required to run HornetQ.
</para>
</listitem>
<listitem>
<para>
- <filename>config</filename> — contains the configuration files required to run JBoss Messaging as a standalone, or within JBoss AS 5. Refer to the User Guide for details about configuring JBoss Messaging.
+ <filename>config</filename> — contains the configuration files required to run HornetQ as a standalone, or within JBoss AS 5. Refer to the User Guide for details about configuring HornetQ.
</para>
</listitem>
<listitem>
<para>
- <filename>docs</filename> — contains guides and Java Docs for JBoss Messaging.
+ <filename>docs</filename> — contains guides and Java Docs for HornetQ.
</para>
</listitem>
<listitem>
@@ -82,20 +82,20 @@
</listitem>
<listitem>
<para>
- <filename>licenses</filename> — contains the licenses for JBoss Messaging.
+ <filename>licenses</filename> — contains the licenses for HornetQ.
</para>
</listitem>
<listitem>
<para>
- <filename>schemas</filename> — contains the XML Schemas used to validate JBoss Messaging configuration files.
+ <filename>schemas</filename> — contains the XML Schemas used to validate HornetQ configuration files.
</para>
</listitem>
</itemizedlist>
</section>
<section id="installation.jboss">
- <title>JBoss Messaging in JBoss Application Server 5.0</title>
+ <title>HornetQ in JBoss Application Server 5.0</title>
<para>
- You can deploy JBoss Messaging 2.0 in <ulink url="http://www.jboss.org/jbossas/">JBoss Application Server 5.0</ulink> (JBoss AS 5). Since JBoss Messaging is not shipped with JBoss AS by default, you must first create new JBoss AS profiles. To do so:
+ You can deploy HornetQ in <ulink url="http://www.jboss.org/jbossas/">JBoss Application Server 5.0</ulink> (JBoss AS 5). Since HornetQ is not shipped with JBoss AS by default, you must first create new JBoss AS profiles. To do so:
</para>
<orderedlist>
<listitem>
@@ -110,7 +110,7 @@
</listitem>
<listitem>
<para>
- Run <command>ant</command> in the <filename>config/jboss-as</filename> directory of your JBoss Messaging installation.
+ Run <command>ant</command> in the <filename>config/jboss-as</filename> directory of your HornetQ installation.
</para>
</listitem>
</orderedlist>
@@ -120,12 +120,12 @@
<itemizedlist>
<listitem>
<para>
- <literal>default-with-jbm2</literal> — corresponds to the JBoss AS <literal>default</literal> profile, and uses JBoss Messaging 2.0 as its JMS provider. In this profile, JBoss Messaging is not clustered.
+ <literal>default-with-jbm2</literal> — corresponds to the JBoss AS <literal>default</literal> profile, and uses HornetQ as its JMS provider. In this profile, HornetQ is not clustered.
</para>
</listitem>
<listitem>
<para>
- <literal>all-with-jbm2</literal> — corresponds to the JBoss AS <literal>all</literal> profile, and uses JBoss Messaging 2.0 as its JMS provider. In this profile, JBoss Messaging is clustered.
+ <literal>all-with-jbm2</literal> — corresponds to the JBoss AS <literal>all</literal> profile, and uses HornetQ as its JMS provider. In this profile, HornetQ is clustered.
</para>
</listitem>
</itemizedlist>
Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Introduction.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Introduction.xml 2010-04-12 02:57:09 UTC (rev 8002)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Introduction.xml 2010-04-12 04:16:22 UTC (rev 8003)
@@ -2,12 +2,12 @@
<chapter id="introduction">
<title>Getting Started</title>
<para>
- This book is a brief guide to downloading, installing and getting started with JBoss Messaging.
+ This book is a brief guide to downloading, installing and getting started with HornetQ.
</para>
<para>
- After you have downloaded and installed JBoss Messaging, we highly recommend running the examples to acquaint yourself with JBoss Messaging and its features.
+ After you have downloaded and installed HornetQ, we highly recommend running the examples to acquaint yourself with HornetQ and its features.
</para>
<para>
- This guide is not intended as a replacement for the JBoss Messaging User Guide. The User Guide contains far greater detail, and should be consulted for further information.
+ This guide is not intended as a replacement for the HornetQ User Guide. The User Guide contains far greater detail, and should be consulted for further information.
</para>
</chapter>
Copied: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Running_HQ.xml (from rev 8002, projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Running_JBM.xml)
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Running_HQ.xml (rev 0)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Running_HQ.xml 2010-04-12 04:16:22 UTC (rev 8003)
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="running">
+ <title>Starting The Server</title>
+ <section id="running.standalone">
+ <title>Standalone JBoss Messaging</title>
+ <para>
+ To run a standalone server, navigate to the <filename>bin</filename> directory via the command line interface. Execute <command>./run.sh</command> (or <command>run.bat</command> on Windows). You should see the following output:
+ </para>
+ <screen>
+bin$ ./run.sh
+
+15:05:54,108 INFO @main [JBMBootstrapServer] Starting JBoss Messaging server
+...
+15:06:02,566 INFO @main [MessagingServerImpl] JBoss Messaging Server version
+2.0.0.BETA1-SNAPSHOT (Stilton, 101) started
+ </screen>
+ <para>
+ If so, JBoss Messaging is now running. If any errors are displayed, or if the server was not started properly, refer to the Troubleshooting section for assistance.
+ </para>
+ <para>
+ Both the run and stop scripts use the configuration listed in <filename>config/stand-alone/non-clustered</filename> by default. You can change the configuration by running <command>./run.sh ../config/stand-alone/non-clustered</command> (or another preferred configuration). The same applies to the stop script and the Windows <filename>bat</filename> files.
+ </para>
+ </section>
+ <section id="running.jboss.as">
+ <title>JBoss Messaging in JBoss Application Server 5</title>
+ <para>
+ To run JBoss Messaging in JBoss AS 5, you must first create JBoss AS profiles for JBoss Messaging, as described in <xref linkend="installation.jboss" />. To run JBoss AS 5 with a non-clustered JBoss Messaging server, go to your <filename>$JBOSS_HOME/bin</filename> directory and type <command>./run.sh -c default-with-jbm2</command>.
+ </para>
+ <screen>
+bin$ ./run.sh -c default-with-jbm2
+
+15:18:35,460 INFO [ServerImpl] Starting JBoss (Microcontainer)...
+15:18:35,462 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.CR1 (build:
+SVNTag=JBoss_5_1_0_CR1 date=200904091504)
+...
+15:19:30,305 INFO [MessagingServerImpl] JBoss Messaging Server version
+2.0.0.BETA1-SNAPSHOT (Stilton, 101) started
+...
+15:19:43,601 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.CR1 (build:
+SVNTag=JBoss_5_1_0_CR1 date=200904091504)] Started in 1m:8s:121ms
+ </screen>
+ </section>
+</chapter>
Deleted: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Running_JBM.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Running_JBM.xml 2010-04-12 02:57:09 UTC (rev 8002)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_Quick_Start_Guide/en-US/Running_JBM.xml 2010-04-12 04:16:22 UTC (rev 8003)
@@ -1,43 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="running">
- <title>Starting The Server</title>
- <section id="running.standalone">
- <title>Standalone JBoss Messaging</title>
- <para>
- To run a standalone server, navigate to the <filename>bin</filename> directory via the command line interface. Execute <command>./run.sh</command> (or <command>run.bat</command> on Windows). You should see the following output:
- </para>
- <screen>
-bin$ ./run.sh
-
-15:05:54,108 INFO @main [JBMBootstrapServer] Starting JBoss Messaging server
-...
-15:06:02,566 INFO @main [MessagingServerImpl] JBoss Messaging Server version
-2.0.0.BETA1-SNAPSHOT (Stilton, 101) started
- </screen>
- <para>
- If so, JBoss Messaging is now running. If any errors are displayed, or if the server was not started properly, refer to the Troubleshooting section for assistance.
- </para>
- <para>
- Both the run and stop scripts use the configuration listed in <filename>config/stand-alone/non-clustered</filename> by default. You can change the configuration by running <command>./run.sh ../config/stand-alone/non-clustered</command> (or another preferred configuration). The same applies to the stop script and the Windows <filename>bat</filename> files.
- </para>
- </section>
- <section id="running.jboss.as">
- <title>JBoss Messaging in JBoss Application Server 5</title>
- <para>
- To run JBoss Messaging in JBoss AS 5, you must first create JBoss AS profiles for JBoss Messaging, as described in <xref linkend="installation.jboss" />. To run JBoss AS 5 with a non-clustered JBoss Messaging server, go to your <filename>$JBOSS_HOME/bin</filename> directory and type <command>./run.sh -c default-with-jbm2</command>.
- </para>
- <screen>
-bin$ ./run.sh -c default-with-jbm2
-
-15:18:35,460 INFO [ServerImpl] Starting JBoss (Microcontainer)...
-15:18:35,462 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.CR1 (build:
-SVNTag=JBoss_5_1_0_CR1 date=200904091504)
-...
-15:19:30,305 INFO [MessagingServerImpl] JBoss Messaging Server version
-2.0.0.BETA1-SNAPSHOT (Stilton, 101) started
-...
-15:19:43,601 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.CR1 (build:
-SVNTag=JBoss_5_1_0_CR1 date=200904091504)] Started in 1m:8s:121ms
- </screen>
- </section>
-</chapter>
More information about the jboss-cvs-commits
mailing list