Author: gaohoward
Date: 2010-09-13 03:44:26 -0400 (Mon, 13 Sep 2010)
New Revision: 9674
Modified:
trunk/examples/jms/non-transaction-failover/readme.html
Log:
typo
Modified: trunk/examples/jms/non-transaction-failover/readme.html
===================================================================
--- trunk/examples/jms/non-transaction-failover/readme.html 2010-09-11 22:16:35 UTC (rev
9673)
+++ trunk/examples/jms/non-transaction-failover/readme.html 2010-09-13 07:44:26 UTC (rev
9674)
@@ -10,7 +10,7 @@
<p>This example demonstrates two servers coupled as a live-backup pair for
high availability (HA), and a client
connection failing over from live to backup when the live server is
crashed.</p>
- <p>Failover behavior differs wether the JMS session is transacter or
not.</p>
+ <p>Failover behavior differs wether the JMS session is transacted or
not.</p>
<p>When a <em>non-transacted</em> JMS session is used, once and
only once delivery is not guaranteed
and it is possible some messages will be lost or delivered twice, depending when
the failover to the backup server occurs.</p>
<p>It is up to the client to deal with such cases. To ensure once and only
once delivery, the client must
@@ -133,4 +133,4 @@
</ol>
</body>
-</html>
\ No newline at end of file
+</html>