ECC queue retry policy

Define retry policies for outbound Web Services that are executed via the ECC Queue table.

Retry policies specify a matching error condition for ECC Queue input records that are a result or response of an output queue record, the interval for retry, and the maximum number of retries. Because it matches on the input queue record, the retry policies only work when an input ECC Queue record is expected, and therefore requires that the outbound messages are queued on the ECC Queue table as well. Advanced matching criteria may be specified using script.

Retry activity

The retry activity records document each attempt to retry the output queue record.

When the current policy is being retried, the Status of the activity will indicate Retrying. When all retries are exhausted, e.g. the maximum number of retries have occurred and the output queue still failed, the Status field will indicate a Failed state. Otherwise, at anytime during the retry, if the request then becomes successful, it indicates Succeeded.

Figure 1. Queue Retry Activity

You may also display the current list of retry activities and their states by selecting the Queue Retry Activity module.

Figure 2. Queue Retry Activities

Retry policy example

This retry policy defines the matching criteria when an UnknownHostException response is received during a SOAPClient (outbound SOAP message invocation) call.

Figure 3. Default Queue Retry Policy

The policy will only match if the Agent, Topic, ECC Name(matches the Name field), and Source fields match that of an input ECC queue record. Additionally, the Condition and Condition script criteria will also have to match "State == error" and the error_string field contains the text java.net.UnknownHostException.

When these conditions are met, and an input record is matched, it will retry the originating output queue record after 15 seconds, and for a maximum of 3 times.