This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/activemq-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 0777eefe4 Automatic Site Publish by Buildbot
0777eefe4 is described below
commit 0777eefe4ee50d5321b8d755508dd6165813f033
Author: buildbot <[email protected]>
AuthorDate: Sat Mar 25 05:48:30 2023 +0000
Automatic Site Publish by Buildbot
---
output/exclusive-consumer.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/output/exclusive-consumer.html b/output/exclusive-consumer.html
index b425dca0f..2c5475a8c 100644
--- a/output/exclusive-consumer.html
+++ b/output/exclusive-consumer.html
@@ -96,7 +96,7 @@
<h3 id="background">Background</h3>
-<p>We maintain the order of messages in queues and dispatch them to consumers
in order. However if you have multiple JMS Sessions and MessageConsumer
instances consuming from the same queue (whether in the same JVM or not), you
will loose the guarantee of processing the messages in order; since the
messages with be processed concurrently in different threads.</p>
+<p>We maintain the order of messages in queues and dispatch them to consumers
in order. However if you have multiple JMS Sessions and MessageConsumer
instances consuming from the same queue (whether in the same JVM or not), you
will loose the guarantee of processing the messages in order; since the
messages will be processed concurrently in different threads.</p>
<p>Sometimes its important to guarantee the order in which messages are
processed. e.g. you don’t want to process the update to an order until an
insert has been done; or to go backwards in time, overwriting an newer update
of an order with an older one etc.</p>
