Open topic with navigation

# Acknowledgment Mode

Durable subscribers acknowledge each message as they process it. However, the client library can transmit acknowledgments to the cluster in either of two modes: synchronous or asynchronous.

Synchronous
Each time the application program acknowledges a message, the client library immediately communicates the acknowledgment to the cluster, and waits for the cluster to confirm that it has safely recorded that acknowledgment.
Asynchronous
The client library gathers batches of acknowledgments, and communicates the batches to the cluster. (The application does not receive confirmation that the cluster has safely recorded the batch of acknowledgments.)

In some situations, batching can improve throughput and latency performance. However, after application failover, durable subscribers could receive duplicate delivery of messages that they have already acknowledged (because the cluster never received the most recent batch of acknowledgments).

Note: Acknowledgment mode as described here is orthogonal to the developer’s choice between automatic acknowledgment versus an explicit acknowledge call.

Acknowledgment mode does not apply to last-value durables.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO FTL® - Enterprise Edition

Copyright © 2009-2024. Cloud Software Group, Inc. All Rights Reserved.