[jboss-cvs] JBoss Messaging SVN: r1838 - in trunk/docs/examples: distributed-topic queue-failover
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Dec 20 06:42:49 EST 2006
Author: ovidiu.feodorov at jboss.com
Date: 2006-12-20 06:42:48 -0500 (Wed, 20 Dec 2006)
New Revision: 1838
Modified:
trunk/docs/examples/distributed-topic/README.html
trunk/docs/examples/queue-failover/README.html
Log:
adjusted the clustered example READMEs
Modified: trunk/docs/examples/distributed-topic/README.html
===================================================================
--- trunk/docs/examples/distributed-topic/README.html 2006-12-20 11:32:19 UTC (rev 1837)
+++ trunk/docs/examples/distributed-topic/README.html 2006-12-20 11:42:48 UTC (rev 1838)
@@ -19,18 +19,6 @@
successful
if both subscribers receive a message sent to the topic.<br>
<br>
-<span style="font-weight: bold;">Note<br>
-</span>
-<div style="margin-left: 40px;">In order to create connections to
-different cluster nodes, the example looks up and downloads
-ConnectionFactories bound in the local JNDI space of each cluster node.
-This is done by explicitely configuring the JNDI client environment to
-point to different physical cluster nodes. This is just a temporary
-solution, used only by the current Alpha release. Subsequent releases
-will use HA-JNDI.<br>
-<span style="font-weight: bold;"></span></div>
-<br>
-<br>
This example relies on having access to a running JBoss Messaging
cluster with at least two nodes. The JBoss Messaging cluster must be
installed and started according to
@@ -124,7 +112,7 @@
[java] MessageListener 2 received message:
Hello!<br>
[java] The example connected to JBoss
-Messaging version 1.2.0.Alpha1 (1.2)<br>
+Messaging version 1.2.0.Beta1 (1.2)<br>
<br>
[java] #####################<br>
[java] ###
Modified: trunk/docs/examples/queue-failover/README.html
===================================================================
--- trunk/docs/examples/queue-failover/README.html 2006-12-20 11:32:19 UTC (rev 1837)
+++ trunk/docs/examples/queue-failover/README.html 2006-12-20 11:42:48 UTC (rev 1838)
@@ -7,33 +7,18 @@
</head>
<body>
<br>
-<h1>JBoss Messaging Queue Consumer Failover Example</h1>
+<h1>JBoss Messaging Queue Failover Example</h1>
$Revision: 1017 $
<h2>Overview</h2>
<br>
-
-This example
-
-This example demonstrates how to write JMS code that connects to a
-JBoss Messaging cluster and sends messages to a distributed topic. The
-client code creates two distinct JMS connections to two different
-cluster nodes. Each connection is then used to create a subscriber for
-the distributed topic. The example is considered
-successful
-if both subscribers receive a message sent to the topic.<br>
+This example demonstrates the transparent failover of a JMS consumer. A
+connection is made on one node of the cluster and two messages are
+sent. A consumer is created and one of the messages is consumed. The
+node the connection is connected to then fails and the connection fails
+over onto the second node. The second message is then consumed using
+the same consumer.<span style="font-weight: bold;"></span>
<br>
-<span style="font-weight: bold;">Note<br>
-</span>
-<div style="margin-left: 40px;">In order to create connections to
-different cluster nodes, the example looks up and downloads
-ConnectionFactories bound in the local JNDI space of each cluster node.
-This is done by explicitely configuring the JNDI client environment to
-point to different physical cluster nodes. This is just a temporary
-solution, used only by the current Alpha release. Subsequent releases
-will use HA-JNDI.<br>
-<span style="font-weight: bold;"></span></div>
<br>
-<br>
This example relies on having access to a running JBoss Messaging
cluster with at least two nodes. The JBoss Messaging cluster must be
installed and started according to
@@ -64,7 +49,7 @@
2. Go to the example's home directory<br>
<br>
<div style="margin-left: 40px;"><span style="font-family: monospace;">cd
-...\examples\distributed-topic</span><br>
+...\examples\queue-failover</span><br>
</div>
<br>
3. Run the example:<br>
@@ -88,56 +73,142 @@
$ ant<br>
Buildfile: build.xml<br>
<br>
-identify:<br>
+identify:
+ <br>
[echo]
-###########################################################################<br>
+###########################################################################
+ <br>
[echo]
#
-Running the DISTRIBUTED TOPIC
-example
-#<br>
+Running the QUEUE FAILOVER example
+
+ #
+ <br>
[echo]
-###########################################################################<br>
+###########################################################################
+ <br>
[echo] The
-topic: testDistributedTopic<br>
+queue: testDistributedQueue
+ <br>
[echo] The client jar:
-../../../output/lib/jboss-messaging-client.jar<br>
+../../../output/lib/jboss-messaging-client.jar
<br>
-sanity-check:<br>
<br>
-init:<br>
- [mkdir] Created dir:
-C:\work\src\svn\messaging\docs\examples\distributed-topic\output<br>
- [mkdir] Created dir:
-C:\work\src\svn\messaging\docs\examples\common\output<br>
+sanity-check:
<br>
-compile:<br>
- [javac] Compiling 2 source files to
-C:\work\src\svn\messaging\docs\examples\common\output<br>
- [javac] Compiling 2 source files to
-C:\work\src\svn\messaging\docs\examples\distributed-topic\output<br>
<br>
-run:<br>
- [java] Distributed topic
-/topic/testDistributedTopic exists<br>
- [java] The message was successfully published
-on the distributed topic<br>
- [java] MessageListener 1 received message:
-Hello!<br>
- [java] MessageListener 2 received message:
-Hello!<br>
+init:
+ <br>
+ <br>
+compile:
+ <br>
+ <br>
+jar:
+ <br>
+ <br>
+deploy:
+ <br>
+ <br>
+sleep:
+ <br>
+ [echo] Sleeping for 5 seconds ...
+ <br>
+ <br>
+run:
+ <br>
+ [java] Distributed queue
+/queue/testDistributedQueue exists
+ <br>
+ [java] The messages were successfully sent to
+the distributed queue
+ <br>
+ [java] Received message: Hello1!
+ <br>
+ [java] 11:12:22,359 ERROR @Timer-0
+[SocketClientInvoker] Got marshalling exception, exiting
+ <br>
+ [java] java.io.IOException: Connection reset
+by peer: socket write error
+ <br>
+ [java] at
+java.net.SocketOutputStream.socketWrite0(Native Method)
+ <br>
+ [java] at
+java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
+ <br>
+ [java] at
+java.net.SocketOutputStream.write(SocketOutputStream.java:136)
+ <br>
+ [java] at
+java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
+ <br>
+ [java] at
+java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
+ <br>
+ [java] at
+java.io.DataOutputStream.flush(DataOutputStream.java:106)
+ <br>
+ [java] at
+org.jboss.serial.io.JBossObjectOutputStream.flush(JBossObjectOutputStream.java:248)
+ <br>
+ [java] at
+org.jboss.jms.server.remoting.JMSWireFormat.serialize(JMSWireFormat.java:1035)
+ <br>
+ [java] at
+org.jboss.jms.server.remoting.JMSWireFormat.write(JMSWireFormat.java:413)
+ <br>
+ [java] at
+org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:518)
+ <br>
+ [java] at
+org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:340)
+ <br>
+ [java] at
+org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:125)
+ <br>
+ [java] at
+org.jboss.remoting.ConnectionValidator.checkConnection(ConnectionValidator.java:184)
+ <br>
+ [java] at
+org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:114)
+ <br>
+ [java] at
+java.util.TimerThread.mainLoop(Timer.java:512)
+ <br>
+ [java] at
+java.util.TimerThread.run(Timer.java:462)
+ <br>
+ [java] 11:12:24,406 INFO @Thread-3
+[HAAspect] HAAspect.ClusteredClientConnectionFactoryDelegate[1]
+completed client-side failover
+ <br>
+ [java] Received message: Hello2!
+ <br>
[java] The example connected to JBoss
-Messaging version 1.2.0.Alpha1 (1.2)<br>
+Messaging version 1.2.0.Beta1 (1.2)
<br>
- [java] #####################<br>
+ <br>
+ [java] #####################
+ <br>
[java] ###
-SUCCESS! ###<br>
- [java] #####################<br>
+SUCCESS! ###
<br>
-BUILD SUCCESSFUL<br>
-Total time: 4 seconds<br>
+ [java] #####################
<br>
<br>
+undeploy:
+ <br>
+ [delete] Deleting:
+C:\dev\jboss-4.0.5.GA\server\messaging-node0\deploy\application-server-killer.jar
+ <br>
+ <br>
+BUILD SUCCESSFUL
+ <br>
+Total time: 41 seconds
+ <br>
+ <br>
+ <br>
+ <br>
</td>
</tr>
</tbody>
More information about the jboss-cvs-commits
mailing list