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 160302abf Automatic Site Publish by Buildbot
160302abf is described below
commit 160302abf2310cdfacc6a74026074f830d155cb4
Author: buildbot <[email protected]>
AuthorDate: Mon Aug 21 13:18:45 2023 +0000
Automatic Site Publish by Buildbot
---
.../nms/providers/activemq/advanced-features/async-sends.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/output/components/nms/providers/activemq/advanced-features/async-sends.html
b/output/components/nms/providers/activemq/advanced-features/async-sends.html
index b60057f23..9d8505f9d 100644
---
a/output/components/nms/providers/activemq/advanced-features/async-sends.html
+++
b/output/components/nms/providers/activemq/advanced-features/async-sends.html
@@ -100,7 +100,7 @@
<p>If you are not using transactions and are sending persistent messages, then
each send is synch and blocks until the broker has sent back an acknowledgement
to the producer that the message has been safely persisted to disk. This ack
provides that guarantee that the message will not be lost but it also costs a
huge latency penalty since the client is blocked.</p>
-<p>Many high performance applications are designed to be tolerate a small
amount of message loss in failure scenarios. If your application has been
designed in this fashion, you can enable the use of async sends to increase
throughput even when using persistent messages.</p>
+<p>Many high performance applications are designed to tolerate a small amount
of message loss in failure scenarios. If your application has been designed in
this fashion, you can enable the use of async sends to increase throughput even
when using persistent messages.</p>
<h3 id="configuring-async-send-using-a-connection-uri">Configuring Async Send
using a Connection URI</h3>
