When a trigger service finishes processing a guaranteed document, Integration Server returns an acknowledgement to the messaging provider. Upon receipt of the acknowledgement, the messaging provider removes its copy of the document from storage. By default, Integration Server returns an acknowledgement for a guaranteed document as soon as it finishes processing the document.

You can increase the number of document acknowledgements returned at one time by changing the value of the Acknowledgement queue size property. The acknowledgement queue is a queue that contains pending acknowledgements for guaranteed documents processed by the webMethods messaging trigger. When the acknowledgement queue size is greater than one, a server thread places a document acknowledgement into the acknowledgement queue after it finishes executing the trigger service. Acknowledgements collect in the queue until a background thread returns them as a group to the sending resource.

If the Acknowledgement queue size is set to one, acknowledgements will not collect in the acknowledgement queue. Instead, Integration Server returns an acknowledgement to the sending resource immediately after the trigger service finishes executing.

If a resource or connection failure occurs before acknowledgements are sent or processed, the transport redelivers the previously processed, but unacknowledged documents. The number of documents redelivered to a webMethods messaging trigger depends on the size on the number of guaranteed documents that were processed but not acknowledged before failure occurred. If exactly-once processing is configured for the webMethods messaging trigger, Integration Server detects the redelivered, guaranteed documents as duplicates and discards them without re-processing them. For more information about exactly-once processing, see Exactly-Once Processing for webMethods Messaging Triggers.

Increasing the size of a webMethods messaging trigger’s acknowledgement queue can provide the following benefits: