The mode used to acknowledge messages after they are consumed
Namespace:
Apache.NMSAssembly: Apache.NMS (in Apache.NMS.dll)
Syntax
| Visual Basic |
|---|
Public Enumeration AcknowledgementMode |
| C# |
|---|
public enum AcknowledgementMode |
| Visual C++ |
|---|
public enum class AcknowledgementMode |
| JavaScript |
|---|
Apache.NMS.AcknowledgementMode = function(); Apache.NMS.AcknowledgementMode.createEnum('Apache.NMS.AcknowledgementMode', false); |
Members
| Member name | Value | Description | |
|---|---|---|---|
| AutoAcknowledge | 0 | With this acknowledgment mode, the session will not acknowledge receipt of a message since the broker assumes successful receipt of a message after the onMessage handler has returned without error. | |
| DupsOkAcknowledge | 1 | With this acknowledgment mode, the session automatically acknowledges a client's receipt of a message either when the session has successfully returned from a call to receive or when the message listener the session has called to process the message successfully returns. Acknowlegements may be delayed in this mode to increase performance at the cost of the message being redelivered this client fails. | |
| ClientAcknowledge | 2 | With this acknowledgment mode, the client acknowledges a consumed message by calling the message's acknowledge method. This acknowledgement acknowledges the given message and all unacknowedged messages that have preceeded it for the session in which the message was delivered. | |
| Transactional | 3 | Messages will be consumed when the transaction commits. | |
| IndividualAcknowledge | 4 | With this acknowledgment mode, the client acknowledges a consumed message by calling the message's acknowledge method. This acknowledgement mode allows the client to acknowledge a single message. This mode is not required to be supported by all NMS providers, however the provider should throw an appropriate exception to indicate that the mode is unsupported. |
See Also
