Open topic with navigation

# Acknowledgment of Message Delivery

A durable subscriber can acknowledge consuming a message to its durable in either of two ways.

Automatic Acknowledgment
With automatic acknowledgment, the base library automatically acknowledges the message when the application callback returns. This choice is appropriate when an application’s callback completely processes the inbound message and then returns.
Explicit Acknowledgment
With explicit acknowledgment, the application program must use the acknowledge call to explicitly acknowledge each message. This choice is appropriate when an application’s callback delegates processing of the inbound message to a separate thread. It could also be appropriate if the application must verify the success of each acknowledgment.

To enable explicit acknowledgment, programs pass a property to the subscriber create call. Otherwise, the default behavior is automatic acknowledgment.

The subscriber must acknowledge each message as received directly from the durable, using the `Acknowledge` call.

Note: The choice between these two mechanisms for acknowledging messages is orthogonal to the administrator’s choice of Acknowledgment Mode: synchronous versus asynchronous.

Acknowledgment is not relevant with 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.