Universal Messaging 10.5 | Migrating webMethods Broker to Software AG Universal Messaging Documentation | Migrating from webMethods Broker to Universal Messaging Guide | Migrating from Broker to Universal Messaging | Pre-migration Considerations | Other Product Considerations
 
Other Product Considerations
Process Engine Trigger Retry Setting
When the Subscription Trigger is configured to retry until Success or has an infinite retry loop, then a document that fails to correlate into a running instance is replayed forever. Integration Server trigger may appear stuck. Universal Messaging does not show the document that is pending acknowledgement, so that the document appears lost. Upon restarting Integration Server, the document is processed again and the cycle may repeat.
To resolve this issue, in Process Engine you can configure the server configuration property watt.prt.suppressCorrelationRetry to true. This suppresses the correlation for a retry. Instead of a transient retry, a regular exception is thrown so there is visibility to the correlation error.
Note:
The watt.prt.suppressCorrelationRetry property changes the default behaviour.