Apache
/
activemq-artemis
mirror of https://github.com/apache/activemq-artemis.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

ARTEMIS-4383: fix a couple of headings butchered in the migration

This commit is contained in:
Robbie Gemmell 2023-08-03 16:27:59 +01:00
parent 5ec3973641
commit 39a13aa07c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/user-manual/pre-acknowledge.adoc
View File

@ -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.