[jboss-cvs] JBossAS SVN: r95080 - projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/stateless-clustered.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Oct 18 23:40:42 EDT 2009
Author: laubai
Date: 2009-10-18 23:40:42 -0400 (Sun, 18 Oct 2009)
New Revision: 95080
Modified:
projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/stateless-clustered/README.html
Log:
Updated stateless-clustered readme files.
Modified: projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/stateless-clustered/README.html
===================================================================
--- projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/stateless-clustered/README.html 2009-10-19 03:28:08 UTC (rev 95079)
+++ projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/stateless-clustered/README.html 2009-10-19 03:40:42 UTC (rev 95080)
@@ -8,68 +8,72 @@
<body>
<h1>Sending JMS messages from a Stateless Clustered Session Bean</h1>
+$ Revision: 5409 $
-<p>$Revision: 5409 $</p>
-
<h2>Overview</h2>
<p>
-This example deploys in a cluster a stateless session bean that can then
-send and receive messages from a queue. This is a very simple example that
-demonstrates using JBoss Messaging in a clustered environment.
-The client uses HA-JNDI to look up the session bean. It then invokes the
-session bean to send a message to a test queue and afterwards consumes the same message.
+ This example deploys a stateless session bean in a cluster. The bean then sends and receives messages from a queue. This is a simple example that demonstrates using JBoss Messaging in a clustered environment. The client uses HA-JNDI to lookup the session bean. The client then invokes the session bean to send a message to a test queue, and then consumes the same message from the queue.
</p>
<p>
-This example relies on having access to a running JBoss Messaging cluster.
-The JBoss Messaging cluster must be installed and started according to
-the "JBoss Messaging Clustered Installation" chapter from the release
-documentation. However, the example will automatically deploy its own
-queue, unless a queue with the same name is already deployed.
+ The example requires access to a running JBoss Messaging cluster installed and started according to the <emphasis>Clustered Installation</emphasis> section in the release documentation. The example automatically deploys its own queue unless a queue with the same name is already deployed.
</p>
-<br>
<p>
-This example also relies on having access to <tt>jboss-messaging-client.jar</tt>
-archive that comes with the release bundle. If you run this example
-from an unzipped installation bundle, the example run script is correctly
-configured to find the client jar. Otherwise, you must modify example's
-<tt>build.xml</tt> accordingly.
+ This example also requires access to the <tt>jboss-messaging-client.jar</tt> archive included in the release bundle. If you run this example from an unzipped installation bundle, the example's run script is already configured to locate the archive. Otherwise, you must modify the example's <tt>build.xml</tt> to specify the location of the archive.
</p>
-<br><br>
-For JBoss5, you should copy all as messaging-node0, configure mysql as a database, make it clustered, and copy it as messaging-node1. Start each instance as:
-<br><br>
-./run -c messaging-node0 -Djboss.service.binding.set=ports-01
-<br><br>
-<br>
-and in another window
-<br><br>
-./run.sh -c messaging-node1 -Djboss.service.binding.set=ports-02 -Djboss.messaging.ServerPeerID=1
-<br><br>
-
-<h2>Running the example</h2>
<p>
-1. Set up the JBOSS_HOME environment variable to point to the JBoss
-instance you deployed JBoss Messaging into. For example, if you
-deployed JBoss Messaging in <tt>C:\jboss-4.2.0.GA\server\messaging-node0\deploy</tt>,
-then your JBOSS_HOME value should be <tt>C:\jboss-4.2.0.GA</tt>.
+ The root directory of your JBoss Enterprise Application Platform installation contains a <span style="font-family: monospace;">server/all/</span> directory.
</p>
+<ol>
+ <li>
+ <p>Copy the <span style="font-family: monospace;">all</span> directory as <span style="font-family: monospace;">messaging-node0</span>:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">cp -r all messaging-node0</span></div>
+ </li>
+ <li>
+ <p>In your new <span style="font-family: monospace;">messaging-node0</span> directory, modify <span style="font-family: monospace;">configure</span> to use a MySQL data source, and the messaging configuration files to make JBoss Messaging clustered.</p>
+ </li>
+ <li>
+ <p>Copy <span style="font-family: monospace;">messaging-node0</span> to another directory as <span style="font-family: monospace;">messaging-node1</span>:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">cp -r messaging-node0 messaging-node1</span></div>
+ </li>
+</ol>
<p>
-2. Go to the example's home directory
+ Start the first instance:
</p>
-<blockquote>
- <pre>cd ...\examples\stateless</pre>
-</blockquote>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">./run.sh -c messaging-node0 -Djboss.service.binding.set=ports-01</span></div>
<p>
-3. Run the example:
+ In a separate window, start the second instance:
</p>
-<blockquote>
- <pre>ant</pre>
-</blockquote>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">./run.sh -c messaging-node1 -Djboss.service.binding.set=ports-02 -Djboss.messaging.ServerPeerID=1</span></div>
+
+
+
+
+<h2>Running the example</h2>
+<ol>
+ <li>
+ <p>Set the JBOSS_HOME environment variable to point to the instance of JBoss Application Server into which you deployed JBoss Messaging. If you deployed JBoss Messaging into <span style="font-family: monospace;">C:\jboss-4.2.0.GA\server\messaging\deploy</span>, your JBOSS_HOME value should be <span style="font-family: monospace;">C:\jboss-4.2.0.GA</span>.</p>
+ </li>
+ <li>
+ <p>Go to the example's home directory:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">cd ...\examples\stateless-clustered</span></div>
+ </li>
+ <li>
+ <p>Run the example:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">ant</span></div>
+ </li>
+</ol>
<p>
-The output of a successful run should be similar to:
+ A successful run should have output similar to the following:
</p>
-<blockquote>
- <pre>$ ant
+
+<table
+ style="width: 90%; text-align: left; font-family: monospace; background-color: rgb(204, 204, 204); margin-left: 40px;"
+ border="1" cellpadding="2" cellspacing="2">
+ <tbody>
+ <tr>
+ <td style="vertical-align: top;"><pre>
+$ ant
Buildfile: build.xml
identify:
@@ -82,17 +86,23 @@
sanity-check:
init:
- [mkdir] Created dir: C:\java\messaging\docs\examples\stateless-clustered\output\classes\META-INF
+ [mkdir] Created dir: C:\java\messaging\docs\examples\stateless-clustered\output\classes
+ \META-INF
[mkdir] Created dir: C:\java\messaging\docs\examples\stateless-clustered\output\lib
compile:
- [javac] Compiling 4 source files to C:\java\messaging\docs\examples\stateless-clustered\output\classes
- [javac] Note: C:\java\messaging\docs\examples\stateless-clustered\src\org\jboss\example\jms\statelessclustered\bean\StatelessClusteredSessionExampleBean.java uses unchecked or unsafe operations.
+ [javac] Compiling 4 source files to C:\java\messaging\docs\examples\stateless-clustered
+ \output\classes
+ [javac] Note: C:\java\messaging\docs\examples\stateless-clustered\src\org\jboss\example
+ \jms\statelessclustered\bean\StatelessClusteredSessionExampleBean.java
+ uses unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
jar:
- [copy] Copying 2 files to C:\java\messaging\docs\examples\stateless-clustered\output\classes\META-INF
- [jar] Building jar: C:\java\messaging\docs\examples\stateless-clustered\output\lib\stateless-clustered-example.jar
+ [copy] Copying 2 files to C:\java\messaging\docs\examples\stateless-clustered\output
+ \classes\META-INF
+ [jar] Building jar: C:\java\messaging\docs\examples\stateless-clustered\output
+ \lib\stateless-clustered-example.jar
deploy:
[copy] Copying 1 file to C:\jboss-4.2.0.GA\server\messaging-node0\farm
@@ -118,17 +128,16 @@
[delete] Deleting: C:\jboss-4.2.0.GA\server\messaging-node0\farm\destinations-farm-service.xml
BUILD SUCCESSFUL
-Total time: 19 seconds
-</pre></blockquote>
+Total time: 19 seconds</pre>
+ </td>
+ </tr>
+ </tbody>
+</table>
-<h2>Troublesooting</h2>
-<h3>1. I get <tt>"javax.jms.JMSSecurityException: User null is NOT authenticated"</tt></h3>
+<h2>Troubleshooting</h2>
+<h3>1. I get a <span style="font-family: monospace;">"javax.jms.JMSSecurityException: User null is NOT authenticated" exception</span></h3>
<p>
-You probably didn't install JBoss Messaging correctly. A fresh JBoss
-Messaging installation requires changes in the security configuration
-of the JBoss instance, specifically a properly configured "<tt>messaging</tt>"
-security domain. Follow the instructions from the "Installation" paragraph of
-the release documentation.
+ JBoss Messaging may not have been installed correctly. A fresh JBoss Messaging installation requires changes to the security configuration of a <span style="font-family: monospace;">default</span> JBoss Application Server instance. In particular it requires a properly configured <tt>messaging</tt> security domain. Follow the instructions in the <emphasis>Installation</emphasis> section of the release documentation.
</p>
</body>
</html>
More information about the jboss-cvs-commits
mailing list