On this Page
Table of Contents | ||||
---|---|---|---|---|
|
Snap type: | Read | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description: | This Snap is used to acknowledge the Java Message Service (JMS) messages read by a JMS consumer used in the upstream Snap. This Snap should always be used in conjunction with JMS Consumer Snap in a pipeline. The JMS Consumer Snap should have the Acknowledgement mode set to CLIENT_ACKNOWLEDGE and Processing mode set to Synchronous.
| |||||||||||||
Prerequisites: | [None] | |||||||||||||
Support and limitations: | Ultra pipelines: Works in Ultra Pipelines.Spark mode: Not supported in /wiki/spaces/SD/pages/1437917 modeTask Pipelines. | |||||||||||||
Account: | Accounts are not used with this Snap. | |||||||||||||
Views: |
| |||||||||||||
Settings | ||||||||||||||
Label | Required. The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline. | |||||||||||||
Recover message | Select this option to explicitly place a failed message back in the JMS Queue by calling recover rather than acknowledge. | |||||||||||||
|
|
Example
A pipeline for JMS Acknowledge may look something like this:
Configure a Mapper Snap to join upstream Snaps to JMS Acknowledge:
The sample output of the JMS Acknowledge Snap may look like this:
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|