Why does the EMS server send an acknowledgement even though the message consumers uses NO_ACKNOWLEDGE mode?
Article ID: KB0085368
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Description:
= = = = = = =
When you monitor the destination using system monitor topics (i.e $sys.monitor.Q.*.<queue_name>), or by enabling tracing on the destination (i.e., "trace" property on the destination and "MSG" option in log_trace), you may find that the EMS server acknowledges the message even though the message consumer uses the NO_ACKNOWLEDGE mode.
Cause:
======
When a consumer uses the NO_ACKNOWLEDGE mode, there is no acknowledgement sent from the consumer to the EMS server over the network. But the EMS server still needs to acknowledge the message to mark that the message has been acked.
Platforms:
========
All
Keywords:
=========
NO_ACKNOWLEDGE
Description:
= = = = = = =
When you monitor the destination using system monitor topics (i.e $sys.monitor.Q.*.<queue_name>), or by enabling tracing on the destination (i.e., "trace" property on the destination and "MSG" option in log_trace), you may find that the EMS server acknowledges the message even though the message consumer uses the NO_ACKNOWLEDGE mode.
Cause:
======
When a consumer uses the NO_ACKNOWLEDGE mode, there is no acknowledgement sent from the consumer to the EMS server over the network. But the EMS server still needs to acknowledge the message to mark that the message has been acked.
Platforms:
========
All
Keywords:
=========
NO_ACKNOWLEDGE
Issue/Introduction
Why does the EMS server send an acknowledgement even though the message consumers uses NO_ACKNOWLEDGE mode?
Feedback
Yes
No
Powered by
