Retry function for sending responses

Know more about the server configuration parameters to configure the retry function for publishing responses to webMethods Integration.

Integration Server uses a transactional publish when sending responses to webMethods Integration. The transactional publish includes a built-in mechanism to recover from intermittent network errors, which can help mitigate the impacts of timeout errors and connection leaks. Integration Server automatically retries any failed transactional publish.

Use the following server configuration parameters to configure the retry function for publishing responses to webMethods Integration.

watt.wmcloud.sendResponse.retry Count - Specifies the maximum number of retry attempts that an on-premises Integration Server makes when a failure occurs when sending a response to webMethods Integration. The default value is 3. A value of 0 indicates that Integration Server will not attempt any retries. Integration Server does not need to be restarted for changes to this parameter to take effect.
watt.wmcloud.sendResponse.retry Dela - Specifies the number of milliseconds that an on-premises Integration Server waits before making another retry attempt after a publish attempt fails. The default value is 1000, that is, one second. Integration Server does not need to be restarted for changes to this parameter to take effect.

If the maximum retry attempts are made and publishing a response to webMethods Integration still fails, the on-premises Integration Server writes an error to the server log. However, if a response payload exceeds the configured maximum buffer limit, then Integration Server does not retry publishing the response to webMethods Integration, but sends an exception to webMethods Integration.

Note: Setting the server log facility 0021 Integration Cloud to the Info level or to a more verbose level might assist with debugging any publishing failures.