This is an automated email from the ASF dual-hosted git repository.
robbie pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/activemq-artemis.git
The following commit(s) were added to refs/heads/main by this push:
new 39a13aa07c ARTEMIS-4383: fix a couple of headings butchered in the
migration
39a13aa07c is described below
commit 39a13aa07caa0f2cbf61385b0c8d5842201591db
Author: Robbie Gemmell <[email protected]>
AuthorDate: Thu Aug 3 16:27:59 2023 +0100
ARTEMIS-4383: fix a couple of headings butchered in the migration
---
docs/user-manual/pre-acknowledge.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/user-manual/pre-acknowledge.adoc
b/docs/user-manual/pre-acknowledge.adoc
index 5291dcc8cc..64c7361cff 100644
--- a/docs/user-manual/pre-acknowledge.adoc
+++ b/docs/user-manual/pre-acknowledge.adoc
@@ -30,7 +30,7 @@ Please note, that if you use pre-acknowledge mode, then you
will lose transactio
This may be stating the obvious but we like to be clear on these things to
avoid confusion!
====
-== Using PRE_ACKNOWLe.g.
+== Using PRE_ACKNOWLEDGE
This can be configured by setting the boolean URL parameter `preAcknowledge`
to `true`.
Alternatively, when using the JMS API, create a JMS Session with the
`ActiveMQSession.PRE_ACKNOWLEDGE` constant.
@@ -41,7 +41,7 @@ Alternatively, when using the JMS API, create a JMS Session
with the `ActiveMQSe
Session session = connection.createSession(false,
ActiveMQJMSConstants.PRE_ACKNOWLEDGE);
----
-== Individual Acknowle.g.
+== Individual Acknowledge
A valid use-case for individual acknowledgement would be when you need to have
your own scheduling and you don't know when your message processing will be
finished.
You should prefer having one consumer per thread worker but this is not
possible in some circumstances depending on how complex is your processing.
For that you can use the individual acknowledgement.
