Integration Server 10.3 | Publish-Subscribe Developer’s Guide | Exactly-Once Processing for Documents Received by webMethods Messaging Triggers | Overview of Exactly-Once Processing | Document Resolver Service | Document Resolver Service and Exceptions
 
Document Resolver Service and Exceptions
At run time, a document resolver service might end because of an exception. How Integration Server proceeds depends on the type of exception and the value of the watt.server.trigger.preprocess.suspendAndRetryOnError property.
*If the document resolver service ends with an ISRuntimeException, and the watt.server.trigger.preprocess.suspendAndRetryOnError property is set to true, Integration Server suspends the trigger and schedules a system task to execute the trigger’s resource monitoring service (if one is specified). Integration Server resumes the trigger and retries trigger execution when the resource monitoring service indicates that the resources used by the trigger are available.
If a resource monitoring service is not specified, you will need to resume the trigger manually (via the Integration Server Administrator or the pub.trigger:resumeProcessing and pub.trigger:resumeRetrieval services). For more information about configuring a resource monitoring service, see Building a Resource Monitoring Service.
*If the document resolver service ends with an ISRuntimeException, and the watt.server.trigger.preprocess.suspendAndRetryOnError property is set to false, Integration Server assigns the document a status of In Doubt, acknowledges the document, and uses the audit subsystem to log the document.
*If the document resolver service ends with an exception other than an ISRuntimeException, Integration Server assigns the document a status of In Doubt, acknowledges the document, and uses the audit subsystem to log the document.