Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.2, 3.0.0
-
Security Level: public (Regular issues)
-
None
Description
There are a number of situations where the transaction manager should respond to failure by waiting a while and trying again.
These include getting a retry error and the backend not being available when the tm starts so a recovery connection is not available.
To solve this we'll need to start by reorienting the relationship between connectors and the tm by giving the tm a NamedXAResourceFactory so it can ask for some way to retry stuff for a given name.
Then we'll need a list of retry tasks and a timer to execute them.