The number of times this transaction has been retried before the present call to the callback.
Handling Post-RTC action errors:
When Post-RTC actions fail, such as acknowleding or sending a message, action handlers try only 10 times with
500 milliseconds sleep. The following parameter scan be configured:
- be.engine.txn.action.retrycount, default is
10.
- be.engine.txn.action.sleeptime, default is
500 milliseconds.
Handling Post-RTC database transaction errors:
In case of database exception, the numer of tries and waits between each tries are handled by the following configuration parameters:
- be.engine.txn.database.retrycount, default is
maximum integer.
- be.engine.txn.database.sleeptime, default is
5000 milliseconds.
After the number of tries are exhausted, the transaction is aborted.
You can also perform additonal actions by registering an error handler fule function as before:
See
be.txn.error function=projectPathToErrorHandlerRuleFunction.
Note: When the number of tries are exhausted and the transactions are aborted, it is likely that the cache and database will be in an inconsistent state. Practice care when setting a limit to the number of retries. Logs shold be also monintored for database related exceptions and immediate action should taken as soon as possible. It is also advised to disable parallel operations if a limit is set to the number of retries. In this case, multiple transactions are committed to the database together and a single database failure can affect multiple of them.
|